embarklabs
/
embark
mirror of https://github.com/embarklabs/embark.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
embark/.gitignore

18 lines
209 B
Plaintext
Raw Normal View History

fix lint; add eslint
2017-10-14 09:24:39 +00:00
.idea
cleanup, consolidate .gitignore files
2018-10-27 15:36:09 +00:00
.node-xmlhttprequest-sync-*
.tern-port
revert caca code
2018-06-26 19:42:49 +00:00
.vscode
add NOTES to gitignore
2017-12-13 16:18:06 +00:00
NOTES
cleanup, consolidate .gitignore files
2018-10-27 15:36:09 +00:00
TODO
dist
embark-*.tgz
node_modules
build: use yarn for reproducible builds and CI yarn.lock files are generated for embark and embark-ui, and their package.json files and other npm related files are updated to support and require using yarn for development of embark itself and for embark's CI.
2018-11-15 23:36:13 +00:00
npm-debug.log*
build: remove and disable npm lock files, rely on pinned dev/deps Buggy behavior related to npm lock files makes the goal of reproducible builds and hassle-free automated releases nearly impossible to achieve at present. With npm's lock files disabled we rely on pinned dependencies (exact versions only in the package.json files of embark and embark-ui) for a hopefully good result. This is an experiment while the project is in an alpha release phase, and if problems are experienced we can return to using npm-shrinkwrap.json / package-lock.json, or we can investigate a transition to the yarn package manager, for ourselves and possibly for our users too.
2018-11-15 20:25:22 +00:00
npm-shrinkwrap.json
cleanup, consolidate .gitignore files
2018-10-27 15:36:09 +00:00
package
build: remove and disable npm lock files, rely on pinned dev/deps Buggy behavior related to npm lock files makes the goal of reproducible builds and hassle-free automated releases nearly impossible to achieve at present. With npm's lock files disabled we rely on pinned dependencies (exact versions only in the package.json files of embark and embark-ui) for a hopefully good result. This is an experiment while the project is in an alpha release phase, and if problems are experienced we can return to using npm-shrinkwrap.json / package-lock.json, or we can investigate a transition to the yarn package manager, for ourselves and possibly for our users too.
2018-11-15 20:25:22 +00:00
package-lock.json
build: use yarn for reproducible builds and CI yarn.lock files are generated for embark and embark-ui, and their package.json files and other npm related files are updated to support and require using yarn for development of embark itself and for embark's CI.
2018-11-15 23:36:13 +00:00
yarn-debug.log*
yarn-error.log*
feature: introduce code coverage
2018-12-11 22:14:26 +00:00
coverage
.nyc_output