mirror of
https://github.com/Unleash/unleash.git
synced 2024-10-18 20:09:08 +02:00
201c86838f
## 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> |
||
|---|---|---|
| .. | ||
| add-to-project.yml | ||
| auto-assign-pr-author.yaml | ||
| build_coverage.yaml | ||
| build_doc_prs.yaml | ||
| build_frontend_prs.yml | ||
| build_prs_jest_report.yaml | ||
| build_prs.yaml | ||
| build.yaml | ||
| check_links.yaml | ||
| codeql-analysis.yml | ||
| continuous-publish-new-version.yaml | ||
| docker_publish_main.yaml | ||
| docker_publish_tags.yaml | ||
| e2e.frontend.yaml | ||
| flag-no-response.yaml | ||
| generate-docs.yaml | ||
| gradual-strict-null-checks.yml | ||
| publish-new-version.yaml | ||
| release_changelog.yml | ||
| release.yaml | ||
| reset_heroku.yml | ||
| update_contributors.yaml | ||