Skip to content

Conversation

@clydin
Copy link
Member

@clydin clydin commented Dec 27, 2022

When using the experimental esbuild-based browser application builder, the --extract-licenses
option will now generate an output licenses file when enabled. This option extracts license
information for each node module package included in the output files of the built code. This
includes JavaScript and CSS output files. The esbuild metafile information generated during the
bundling steps is used as the source of information regarding what input files where included and
where they are located. A path segment of node_modules is used to indicate that a file belongs
to a package and its license should be include in the output licenses file.

The package name and license field are extracted from the package.json file for the
package. If a license file (e.g., LICENSE) is present in the root of the package, it
will also be included in the output licenses file. Custom licenses as defined by the recommended
npm custom license text (SEE LICENSE IN <filename>) will also be extracted and included in the
output license file. For additional information regarding the license field in a package.json,
see https://docs.npmjs.com/cli/v9/configuring-npm/package-json#license.

@clydin clydin added state: blocked target: minor This PR is targeted for the next minor release labels Dec 27, 2022
@angular-robot angular-robot bot added the detected: feature PR contains a feature commit label Dec 27, 2022
@clydin clydin force-pushed the esbuild/extract-licenses branch from 0c21239 to 00e9693 Compare December 27, 2022 23:30
…traction for esbuild builder

When using the experimental esbuild-based browser application builder, the `--extract-licenses`
option will now generate an output licenses file when enabled. This option extracts license
information for each node module package included in the output files of the built code. This
includes JavaScript and CSS output files. The esbuild metafile information generated during the
bundling steps is used as the source of information regarding what input files where included and
where they are located. A path segment of `node_modules` is used to indicate that a file belongs
to a package and its license should be include in the output licenses file.

The package name and license field are extracted from the `package.json` file for the
package. If a license file (e.g., `LICENSE`) is present in the root of the package, it
will also be included in the output licenses file. Custom licenses as defined by the recommended
npm custom license text (`SEE LICENSE IN <filename>`) will also be extracted and included in the
output license file. For additional information regarding the license field in a `package.json`,
see https://docs.npmjs.com/cli/v9/configuring-npm/package-json#license.
@clydin clydin force-pushed the esbuild/extract-licenses branch from 00e9693 to 44b098e Compare January 3, 2023 15:38
@clydin clydin added action: review The PR is still awaiting reviews from at least one requested reviewer and removed state: blocked labels Jan 3, 2023
@alan-agius4 alan-agius4 added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Jan 9, 2023
@angular-robot angular-robot bot merged commit 09af707 into angular:main Jan 9, 2023
@clydin clydin deleted the esbuild/extract-licenses branch January 9, 2023 15:00
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Feb 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker detected: feature PR contains a feature commit target: minor This PR is targeted for the next minor release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants