Files
meteor/packages/code-prettify/package.js
David Glasser 43b4b30205 Release PLUGINS-PREVIEW@1
This included removing some internal version constraints. It would be
nice if package A could say "use B@2.0.0" (when both have changed), but
when they're both in the release, we need to make a release that has a
B@2.0.0-rc in it, which doesn't match that constraint. Fortunately,
constraints aren't necessary within a release anyway.
2015-07-22 23:19:11 -07:00

22 lines
600 B
JavaScript

// Source: http://code.google.com/p/google-code-prettify
// XXX this sucks. I would much rather do this processing at
// bundle-time on the server, not in the client. (though I'd like to
// support both..)
var path = Npm.require('path');
Package.describe({
summary: "Syntax highlighting of code, from Google",
version: "1.0.4-plugins.0"
});
// XXX this code dumps symbols into the global namespace (directly
// onto 'window'.) we need to fix that.
Package.onUse(function (api) {
api.addFiles([
'prettify.js',
'prettify.css',
path.join('styles', 'sunburst.css')], "client");
});