Simplify developer experience? about contenttools HOT 3 CLOSED

Thank you for the feedback. Right now all dependencies are included with the package in a folder called '/externals' and the build process concatenates them to the start of the final output file - which 'hands up' isn't ideal and moving towards correct node/npm support is a goal for the very near future.

To provide a very quick overview: ContentTools is a collection of libraries all written in CoffeeScript (this is up for debate #10), the collection includes:

• FSM (https://github.com/GetmeUK/FSM) [no dependencies]
• HTMLString (https://github.com/GetmeUK/HTMLString) [depends on FSM]
• ContentSelect (https://github.com/GetmeUK/ContentSelect) [no dependencies]
• ContentEdit (https://github.com/GetmeUK/ContentEdit) [depends on HTMLString, ContentSelect]
• ContentEdit (https://github.com/GetmeUK/ContentTools) [depends on ContentEdit]

Full reply to original HackerNews question available here: https://news.ycombinator.com/item?id=10310256

from contenttools.

Just wanted to drop a note here mentioning it would be nice to see this migrate to a more standardized npm + (rollup/browserify/webpack/babel/whatever) module architecture.

from contenttools.

This issue has partially been resolved as ContentTools (and all other related libraries) are now registered on Bower. NPM registration is still planned but the issue has been re-raised specifically in that context: #174

from contenttools.