Publish the build version on NPM. about angular-marked

[Hypercubed]

Sure, I can do that. But can I ask... most npm packages do not include the build files (i.e. browserified files), how are you managing other packages? Would it be better in the long run for you to include browserify (or equivalent) in your build tools? It is helpful for me to understand how people are using this package. Thank you.

[qraynaud]

Well, all other packages (including angular files) I'm using (except lodash) do provide "packaged versions" in a "dist" (or likewise) folder.

I mean there is sometimes a min file (like for angular.js wich provides both) but you can at least find a file with all the src files concatenated in them and protected by an UMD or something like that. If they are not minified I do the minification myself for the production env.

The thing that is always possible is to include the files « as is » for the dev env without having an error raised in the console (here caused by module.exports = "…").

For the record, right now I need bower for only two packages: lodash and angular-marked. I would love to get rid of bower though…

[Hypercubed]

Thank you for the feedback. It is difficult to know exactly all ways a package will be used.

Version 1.0.1 now includes the browserify version. Please let me know if you have issues.

[qraynaud]

Thanks a lot to you for your reactivity! I'll close this and reopen it if I find something "wrong".

Thanks again!