archetype and build type for crt/updater/ide #643
Conversation
- make snapshot.json - copy package/json to /static/package.json - no /index.html, /cache.manifest
remove append flag from write
Thanks Haibiao Chen for the fix
|
For finding custom archetypes, I would have preferred if it used the resource store ( |
create-mojit-default one per orig docs
|
@drewfish We discussed this when I tried implementing the hybrid archetype as a package-- RS doesn't support it, and the existing create.js doesn't use mojito or the resource store at all yet. This feature is pretty minor in terms of code changes, and may be useful for the IDE/CRT integration. I agree we should support of npm packaging of archetypes in the future, as planned, so that archetypes can be sanely shared, versioned, etc. If that future/planned feature blocks this entire PR, let me know and I'll make a new one without the |
|
OK cool. I don't imagine that anything in this PR will block future use of archetypes delivered via NPM modules. So, +1. |
new archetype: mojito create app hybrid myapp new build type: mojito build hybrid path/to/packages/dir new custom archetypes: mojito create custom path/to/your/archetype mything
new archetype:
mojito create app hybrid myappnew build type:
mojito build hybrid path/to/packages/dirhttps://gist.github.com/26623632f9c593be9078
though the build command was split into seven different sub modules, the eloc count is lower at the moment.
new support for user-specified archetypes:
mojito create custom path/to/your/archetype mything