Publish npm package

[hoho]

I want to create Gulp plugin for server-side highlighting. Your repo has package.json and Prism works in node.js, but the package is currently not published. Is there any reason for not publishing the package?

[iamvdo]

Same question!

I'm using prism from npm (targeting the gh-pages branch) but all new commits break old code! I have to specify a specific commit in my package.json :/ Not using semantic version is really disappointed.

[jsmreese]

+1

I periodically download the latest version (under the assumption that it must have a few useful improvements) but I have no idea what version I was using or what's changed in the interim.

Publishing a package or just simply tagging release versions would fix that!

Even something as simple as incrementing the last version point value would really help, and would orient me in the project: I have version 0.0.24 and version 0.0.43 was just published...

[apfelbox]

Working on this, together with #231

[LeaVerou]

Working on this, together with #231

Awesome, thank you so much @apfelbox! I really can't put my gratitude in words about your help on this project so far! You rock! :D

[Golmote]

npm package is now published, with the latest release version. We'll try to keep it that way in the future. ;)