Feature #33318
provide a list of JavaScript dependencies that can be ignored during package building
Difficulty:
Triaged:
No
Description
package.json contains dependencies, that are only required for tests and dev, but not building of assets (and packages),
it would be nice if we had this as a list somewhere, so it can be consumed by packaging tools
Related issues
Associated revisions
Refs #33318 - add a script to filter package.json
History
#1
Updated by Evgeni Golov over 1 year ago
Updated by - Related to Bug #33317: better differentiate between build, develop and test dependencies for JavaScript added
#2
Updated by The Foreman Bot over 1 year ago
Updated by - Assignee set to Evgeni Golov
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/8729 added
#3
Updated by The Foreman Bot over 1 year ago
- Fixed in Releases 3.1.0 added
#4
Updated by Evgeni Golov over 1 year ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman|7b682c60a2bf6332e663362470d356505ba2c6bc.
#5
Updated by The Foreman Bot over 1 year ago
- Pull request https://github.com/theforeman/foreman/pull/8731 added
#6
Updated by The Foreman Bot over 1 year ago
- Pull request https://github.com/theforeman/foreman/pull/8736 added
#7
Updated by Evgeni Golov over 1 year ago
- Fixed in Releases 3.0.0 added
- Fixed in Releases deleted (
3.1.0)
Fixes #33318 - add JS packages to be excluded for packaging
this list is taken from `update-requirements` in foreman-packaging and
is supposed to be the central place to manage those excludes from here
on. `update-requirements` will be updated to use this file.