Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 21, 2022

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@ampproject/remapping 1.0.2 -> 1.1.1 age adoption passing confidence
@babel/core (source) 7.16.10 -> 7.16.12 age adoption passing confidence
esbuild 0.14.12 -> 0.14.13 age adoption passing confidence
esbuild-wasm 0.14.12 -> 0.14.13 age adoption passing confidence
resolve 1.21.1 -> 1.22.0 age adoption passing confidence
verdaccio (source) 5.4.0 -> 5.5.0 age adoption passing confidence
webpack 5.66.0 -> 5.67.0 age adoption passing confidence

Release Notes

ampproject/remapping

v1.1.1

Compare Source

v1.1.0

Compare Source

babel/babel

v7.16.12

Compare Source

🐛 Bug Fix
evanw/esbuild

v0.14.13

Compare Source

  • Be more consistent about external paths (#​619)

    The rules for marking paths as external using --external: grew over time as more special-cases were added. This release reworks the internal representation to be more straightforward and robust. A side effect is that wildcard patterns can now match post-resolve paths in addition to pre-resolve paths. Specifically you can now do --external:./node_modules/* to mark all files in the ./node_modules/ directory as external.

    This is the updated logic:

    • Before path resolution begins, import paths are checked against everything passed via an --external: flag. In addition, if something looks like a package path (i.e. doesn't start with / or ./ or ../), import paths are checked to see if they have that package path as a path prefix (so --external:@​foo/bar matches the import path @foo/bar/baz).

    • After path resolution ends, the absolute paths are checked against everything passed via --external: that doesn't look like a package path (i.e. that starts with / or ./ or ../). But before checking, the pattern is transformed to be relative to the current working directory.

  • Attempt to explain why esbuild can't run (#​1819)

    People sometimes try to install esbuild on one OS and then copy the node_modules directory over to another OS without reinstalling. This works with JavaScript code but doesn't work with esbuild because esbuild is a native binary executable. This release attempts to offer a helpful error message when this happens. It looks like this:

    $ ./node_modules/.bin/esbuild
    ./node_modules/esbuild/bin/esbuild:106
              throw new Error(`
              ^
    
    Error:
    You installed esbuild on another platform than the one you're currently using.
    This won't work because esbuild is written with native code and needs to
    install a platform-specific binary executable.
    
    Specifically the "esbuild-linux-arm64" package is present but this platform
    needs the "esbuild-darwin-arm64" package instead. People often get into this
    situation by installing esbuild on Windows or macOS and copying "node_modules"
    into a Docker image that runs Linux, or by copying "node_modules" between
    Windows and WSL environments.
    
    If you are installing with npm, you can try not copying the "node_modules"
    directory when you copy the files over, and running "npm ci" or "npm install"
    on the destination platform after the copy. Or you could consider using yarn
    instead which has built-in support for installing a package on multiple
    platforms simultaneously.
    
    If you are installing with yarn, you can try listing both this platform and the
    other platform in your ".yarnrc.yml" file using the "supportedArchitectures"
    feature: https://yarnpkg.com/configuration/yarnrc/#supportedArchitectures
    Keep in mind that this means multiple copies of esbuild will be present.
    
    Another alternative is to use the "esbuild-wasm" package instead, which works
    the same way on all platforms. But it comes with a heavy performance cost and
    can sometimes be 10x slower than the "esbuild" package, so you may also not
    want to do that.
    
        at generateBinPath (./node_modules/esbuild/bin/esbuild:106:17)
        at Object.<anonymous> (./node_modules/esbuild/bin/esbuild:161:39)
        at Module._compile (node:internal/modules/cjs/loader:1101:14)
        at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
        at Module.load (node:internal/modules/cjs/loader:981:32)
        at Function.Module._load (node:internal/modules/cjs/loader:822:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
        at node:internal/main/run_main_module:17:47
    
browserify/resolve

v1.22.0

Compare Source

verdaccio/verdaccio

v5.5.0

Compare Source

Features

TL;DR

Web User Interface Improvements

The current user interface for this version is exactly the same used on the next major release, the verdaccio/ui repository has been archived, one single UI is much easier to maintain and also to share features between the future major release and the stable one.

The translations were migrated from the source code to the crowdin platform for the User interface which ensure repeated words are not translated twice and also crowding provides a nice interface for contributions, the latest translations are pulled on every release automcatically.

  • Add new options to the web disable login and pkg managers (#​2947) (1a7b1ee)

    • Users are able to select which package managers you want to enabled on the web user interface ref #​2226
    • Users are able to enable/disable login on web and endpoints option ref #​2228 (this is another security layer which some users might be interested to disable)
web:
  pkgManagers:
    - npm
    - yarn
    - pnpm
  login: true      
Improve language switch ui and package manager info
  • Remove the language switch as autocomplete, add info how to contribute to translations
  • Convert info dialog to be able host more information, learn how to use registry with Yarn 2 and add links to documentation.

2022-01-22_13-17
2022-01-20_22-09

Bug Fixes

⚠️ The marked dependency has been updated to v4 which was marked a security upgrade through the @verdaccio/readme dependency.

Announcements

The next month is the talk at Node.js Congress 2022, you can craft your own badge 😊 here, please share it with your colleagues and 👍🏼 if you want like this tweet.

Screenshot 2022-01-22 165430
webpack/webpack

v5.67.0

Compare Source

Features

  • add 'outputPath' configuration option for resource asset modules
  • support Trusted Types in eval source maps
  • experiments.css
    • allow to generate only exports for css in node
    • add SyncModuleIdsPlugin to sync module ids between server and client compilation
    • add more options to the DeterministicModuleIdsPlugin to allow to generate equal ids

Developer Experience

  • limit data url module name in stats printer
  • allow specific description for CLI options
  • improve space limiting algorithm in stats printing to show partial lists
  • add null to errors in callbacks
  • fix call signature types of addChunkInGroup

Bugfixes

  • avoid reporting non-existant package.jsons as dependencies
  • experiments.css
    • fix missing css runtime when only initial css is used
    • fix css hmr support
    • bugfixes to css modules
  • fix cache serialization for CreateScriptUrlDependency
  • fix data url content when processed by a loader
  • fix regexp in identifiers that include |
  • fix ProfilingPlugin for watch scenarios
  • add layer to module names and identifiers
    • this avoid random module id changes when additional modules are added to another layer
  • provide hashFunction parameter to DependencyTemplates to allow customizing it there
  • fix HMR when experiments.lazyCompilation is enabled
  • store url as Buffer to avoid serialization warnings
  • exclude webpack-hot-middleware/client from lazy compilation

Contributing

  • remove travis configuration
  • improve spell checking

Configuration

📅 Schedule: "after 10pm every weekday,before 4am every weekday,every weekend" in timezone America/Tijuana.

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

Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

👻 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 WhiteSource Renovate. View repository job log here.

@renovate renovate bot added action: merge The PR is ready for merge by the caretaker target: minor This PR is targeted for the next minor release labels Jan 21, 2022
@renovate renovate bot changed the title build: update all non-major dependencies build: update all non-major dependencies - autoclosed Jan 21, 2022
@renovate renovate bot closed this Jan 21, 2022
@renovate renovate bot deleted the renovate/all-minor-patch branch January 21, 2022 11:53
@renovate renovate bot changed the title build: update all non-major dependencies - autoclosed build: update all non-major dependencies Jan 21, 2022
@renovate renovate bot reopened this Jan 21, 2022
@renovate renovate bot restored the renovate/all-minor-patch branch January 21, 2022 19:59
@alan-agius4 alan-agius4 added target: rc This PR is targeted for the next release-candidate and removed target: minor This PR is targeted for the next minor release labels Jan 21, 2022
@renovate renovate bot changed the title build: update all non-major dependencies build: update dependency webpack to v5.67.0 Jan 21, 2022
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 1d41995 to bec77c1 Compare January 21, 2022 21:21
@renovate renovate bot changed the title build: update dependency webpack to v5.67.0 build: update all non-major dependencies Jan 22, 2022
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 97c4d89 to 9642506 Compare January 22, 2022 20:29
@alan-agius4 alan-agius4 linked an issue Jan 23, 2022 that may be closed by this pull request
15 tasks
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9642506 to fdeaf66 Compare January 23, 2022 09:21
@alan-agius4 alan-agius4 force-pushed the renovate/all-minor-patch branch from fdeaf66 to 61a6881 Compare January 24, 2022 10:03
@alan-agius4 alan-agius4 force-pushed the renovate/all-minor-patch branch from 61a6881 to 8b9d441 Compare January 24, 2022 10:57
@alan-agius4 alan-agius4 merged commit e9684b2 into master Jan 24, 2022
@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 24, 2022
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 target: rc This PR is targeted for the next release-candidate
Projects
None yet
1 participant