1
0
mirror of https://github.com/Unleash/unleash.git synced 2024-12-28 00:06:53 +01:00
unleash.unleash/.gitignore
Gastón Fournier 201c86838f
Test npm publish (#3554)
## About the changes

https://github.blog/changelog/2022-10-24-npm-v9-0-0-released/ introduced
a breaking change in the way they handle files inside package.json which
caused some issues with the way we pack and distribute Unleash:

> npm pack now follows a strict order of operations when applying ignore
rules. If a files array is present in the package.json, then rules in
.gitignore and .npmignore files from the root will be ignored.

What we discovered is that when having a nested .gitignore (the one we
have inside frontend), `npm publish` was taking that nested .gitignore
into account (despite the fact that we also have a package.json with
files inside the same folder). We tricked this by removing the `build`
folder from `frontend/.gitignore` and instead adding it into the root
`.gitignore` which is being ignored by `npm publish` following what's
stated in the release note above.

-----------------

Co-authored-by: Gard Rimestad <gard@getunleash.io>
2023-04-18 15:44:19 +02:00

59 lines
778 B
Plaintext

node_modules
lerna-debug
npm-debug
.DS_Store
/dist
# Logs
logs
*.log
# Runtime data
pids
*.pid
*.seed
# Directory for instrumented libs generated by jscoverage/JSCover
lib-cov
# Coverage directory used by tools like istanbul
# coverage
coverage/lcov-report
# Compiled binary addons (http://nodejs.org/api/addons.html)
build/Release
# liquibase stuff
/sql
unleash-db.jar
unleash-server.tar.gz
# idea stuff:
.idea/*
.vagrant/
# Visual Studio Code
jsconfig.json
typings
.vscode
.nyc_output
# We use yarn.lock
package-lock.json
# Website stuff
/website/build
/website/backers.json
/website/node_modules
/website/translated_docs
/website/i18n/*
.env
# Ignore frontend build
frontend/build
# Generated docs
website/docs/reference/api/**/sidebar.js
website/docs/generated