Skip to content

Conversation

@angular-robot
Copy link
Contributor

@angular-robot angular-robot commented Dec 15, 2022

This PR contains the following updates:

Package Type Update Change
build_bazel_rules_nodejs http_archive minor 5.7.3 -> 5.8.0
cacache dependencies patch 17.0.3 -> 17.0.4
cacache devDependencies patch 17.0.3 -> 17.0.4
esbuild optionalDependencies patch 0.16.6 -> 0.16.7
esbuild devDependencies patch 0.16.6 -> 0.16.7
esbuild-wasm dependencies patch 0.16.6 -> 0.16.7
esbuild-wasm devDependencies patch 0.16.6 -> 0.16.7
pacote dependencies patch 15.0.7 -> 15.0.8
pacote devDependencies patch 15.0.7 -> 15.0.8

Release Notes

bazelbuild/rules_nodejs

v5.8.0

Compare Source

This release contains Bazel modules only, there are no accompanying npm packages because they weren't affected.

Upgrade with:

http_archive(
    name = "build_bazel_rules_nodejs",
    sha256 = "dcc55f810142b6cf46a44d0180a5a7fb923c04a5061e2e8d8eb05ccccc60864b",
    urls = ["https://github.com/bazelbuild/rules_nodejs/releases/download/5.8.0/rules_nodejs-5.8.0.tar.gz"],
)

### or for core module
http_archive(
    name = "rules_nodejs",
    sha256 = "08337d4fffc78f7fe648a93be12ea2fc4e8eb9795a4e6aa48595b66b34555626",
    urls = ["https://github.com/bazelbuild/rules_nodejs/releases/download/5.8.0/rules_nodejs-core-5.8.0.tar.gz"],
)

What's Changed

Full Changelog: bazel-contrib/rules_nodejs@5.7.3...5.8.0

npm/cacache

v17.0.4

Compare Source

Dependencies
evanw/esbuild

v0.16.7

Compare Source

  • Include file loader strings in metafile imports (#​2731)

    Bundling a file with the file loader copies that file to the output directory and imports a module with the path to the copied file in the default export. Previously when bundling with the file loader, there was no reference in the metafile from the JavaScript file containing the path string to the copied file. With this release, there will now be a reference in the metafile in the imports array with the kind file-loader:

     {
       ...
       "outputs": {
         "out/image-55CCFTCE.svg": {
           ...
         },
         "out/entry.js": {
           "imports": [
    +        {
    +          "path": "out/image-55CCFTCE.svg",
    +          "kind": "file-loader"
    +        }
           ],
           ...
         }
       }
     }
  • Fix byte counts in metafile regarding references to other output files (#​2071)

    Previously files that contained references to other output files had slightly incorrect metadata for the byte counts of input files which contributed to that output file. So for example if app.js imports image.png using the file loader and esbuild generates out.js and image-LSAMBFUD.png, the metadata for how many bytes of out.js are from app.js was slightly off (the metadata for the byte count of out.js was still correct). The reason is because esbuild substitutes the final paths for references between output files toward the end of the build to handle cyclic references, and the byte counts needed to be adjusted as well during the path substitution. This release fixes these byte counts (specifically the bytesInOutput values).

  • The alias feature now strips a trailing slash (#​2730)

    People sometimes add a trailing slash to the name of one of node's built-in modules to force node to import from the file system instead of importing the built-in module. For example, importing util imports node's built-in module called util but importing util/ tries to find a package called util on the file system. Previously attempting to use esbuild's package alias feature to replace imports to util with a specific file would fail because the file path would also gain a trailing slash (e.g. mapping util to ./file.js turned util/ into ./file.js/). With this release, esbuild will now omit the path suffix if it's a single trailing slash, which should now allow you to successfully apply aliases to these import paths.

npm/pacote

v15.0.8

Compare Source

Dependencies

Configuration

📅 Schedule: Branch creation - "after 10:00pm every weekday,before 4:00am every weekday,every weekend" in timezone America/Tijuana, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

@angular-robot angular-robot added action: merge The PR is ready for merge by the caretaker target: minor This PR is targeted for the next minor release labels Dec 15, 2022
@angular-robot angular-robot bot added the area: build & ci Related the build and CI infrastructure of the project label Dec 15, 2022
@angular-robot angular-robot force-pushed the ng-renovate/all-minor-patch branch from 1fe8b1c to f2b54b7 Compare December 15, 2022 20:05
@angular-robot angular-robot bot merged commit a9c0982 into angular:main Dec 15, 2022
@angular-robot angular-robot deleted the ng-renovate/all-minor-patch branch December 15, 2022 21:06
@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 Jan 15, 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 area: build & ci Related the build and CI infrastructure of the project 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