embark/embark-ui/.gitignore

# See https://help.github.com/ignore-files/ for more about ignoring files.

# dependencies
/node_modules

# testing
/coverage

# production
/build

# misc
.DS_Store
.env.local
.env.development.local
.env.test.local
.env.production.local

npm-debug.log*
yarn-debug.log*
yarn-error.log*

# lock files
npm-shrinkwrap.json
package-lock.json
Adding embark ui 2018-08-01 10:19:11 +01:00			`# See https://help.github.com/ignore-files/ for more about ignoring files.`

			`# dependencies`
			`/node_modules`

			`# testing`
			`/coverage`

			`# production`
			`/build`

			`# misc`
			`.DS_Store`
			`.env.local`
			`.env.development.local`
			`.env.test.local`
			`.env.production.local`

			`npm-debug.log*`
			`yarn-debug.log*`
			`yarn-error.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 14:25:22 -06:00
			`# lock files`
			`npm-shrinkwrap.json`
			`package-lock.json`