embark/embark-ui/.npmignore

.env
.env.*
.eslintrc
.yarnrc
config
node_modules
npm-debug.log*
npm-shrinkwrap.json
package-lock.json
public
scripts
src
yarn-debug.log*
yarn-error.log*
yarn.lock
don't gen source maps for production builds of embark-ui don't include .env files in the pkg tarball 2018-10-28 12:52:28 +01:00			`.env`
			`.env.*`
build(packaging): reorg sources for transpilation with Babel Allow for embark sources to be authored in TypeScript and/or JavaScript, and to make use of upcoming features of the JS language. Sources in the src/ directory are transpiled into the dist/ directory, and npm-scripts are provided to support and automate various aspect of the build process. Source map support is enabled at runtime, i.e. when invoking the embark cli and running embark's test suite. 2018-11-11 15:08:55 -06:00			`.eslintrc`
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 17:36:13 -06:00			`.yarnrc`
rev embark-ui .npmignore 2018-10-25 08:26:48 -05:00			`config`
			`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 17:36:13 -06: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 14:25:22 -06:00			`npm-shrinkwrap.json`
			`package-lock.json`
rev embark-ui .npmignore 2018-10-25 08:26:48 -05:00			`public`
			`scripts`
			`src`
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 17:36:13 -06:00			`yarn-debug.log*`
			`yarn-error.log*`
			`yarn.lock`