thelounge/.npmignore

# This file must not contain generated assets listed in .gitignore.
# npm-debug.log and node_modules/ are ignored by default.
# See https://docs.npmjs.com/misc/developers#keeping-files-out-of-your-package

client/views/
coverage/
scripts/
test/
.editorconfig
.eslintignore
.eslintrc.yml
.gitattributes
.gitignore
.istanbul.yml
.npmignore
.stylelintrc
.travis.yml
appveyor.yml
Gruntfile.js
Ignore unnecessary files at release time - `client/views/` contains templates whose built version is provided with each releases - `.gitignore` doesn't appear in our releases, but I'm not sure if this comes from npm itself or Travis CI publishing for us. Adding it here for completeness. - Surprisingly, `.npmignore` itself is not ignored... - All other files and directories are for development purposes only 2016-07-14 05:57:56 +02:00			`# This file must not contain generated assets listed in .gitignore.`
Remove compiled assets and generate them at prepublish time - Remove minified libs and compiled templates - Add a `prepublish` script to build assets, that run on `npm install` and right before publishing See https://docs.npmjs.com/misc/scripts - Include these compiled assets to the `.gitignore` file - Add an empty .npmignore to make sure the compiled assets are not ignored when publishing https://docs.npmjs.com/misc/developers#keeping-files-out-of-your-package - Update the README to reflect changes in development Note that the Travis CI configuration does not need any tweaking because it cleans up all extra and changed files, up to publishing on npm. That is, right before `prepublish` gets run. See https://docs.travis-ci.com/user/deployment/npm#Releasing-build-artifacts 2016-02-18 07:01:37 +01:00			`# npm-debug.log and node_modules/ are ignored by default.`
			`# See https://docs.npmjs.com/misc/developers#keeping-files-out-of-your-package`
Add code coverage 2016-06-16 08:42:24 +02:00
Ignore unnecessary files at release time - `client/views/` contains templates whose built version is provided with each releases - `.gitignore` doesn't appear in our releases, but I'm not sure if this comes from npm itself or Travis CI publishing for us. Adding it here for completeness. - Surprisingly, `.npmignore` itself is not ignored... - All other files and directories are for development purposes only 2016-07-14 05:57:56 +02:00			`client/views/`
Add code coverage 2016-06-16 08:42:24 +02:00			`coverage/`
Ignore unnecessary files at release time - `client/views/` contains templates whose built version is provided with each releases - `.gitignore` doesn't appear in our releases, but I'm not sure if this comes from npm itself or Travis CI publishing for us. Adding it here for completeness. - Surprisingly, `.npmignore` itself is not ignored... - All other files and directories are for development purposes only 2016-07-14 05:57:56 +02:00			`scripts/`
			`test/`
			`.editorconfig`
			`.eslintignore`
			`.eslintrc.yml`
			`.gitattributes`
			`.gitignore`
			`.istanbul.yml`
			`.npmignore`
			`.stylelintrc`
			`.travis.yml`
			`appveyor.yml`
			`Gruntfile.js`