Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update dependency @rollup/plugin-node-resolve to v15 #82

Merged
merged 1 commit into from
Aug 23, 2023
Merged

Update dependency @rollup/plugin-node-resolve to v15 #82

merged 1 commit into from
Aug 23, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 20, 2023 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@rollup/plugin-node-resolve (source) 9.0.0 -> 15.2.1 age adoption passing confidence

Release Notes

rollup/plugins (@​rollup/plugin-node-resolve)

v15.2.1

Compare Source

2023-08-22

Bugfixes
  • fix: Implement package exports / imports resolution algorithm according to Node documentation #​1549

v15.2.0

Compare Source

2023-08-17

Features
  • feat: pass original importee to secondary resolve #​1557

v15.1.0

Compare Source

2023-05-30

Features
  • feat: Resolve js/jsx/mjs/cjs imports from TypeScript files #​1498

v15.0.2

Compare Source

2023-04-04

Bugfixes
  • fix: bump is-builtin-module version, imports with a trailing slash #​1424

v15.0.1

Compare Source

2022-10-21

Updates
  • chore: update rollup dependencies (3038271)

v15.0.0

Compare Source

2022-10-10

Breaking Changes

v14.1.0

Compare Source

2022-09-12

Features
  • feat: add new option, modulePaths (#​1104)

v14.0.1

Compare Source

2022-09-08

Bugfixes
  • fix: handle circular commonjs (#​1259)

v14.0.0

2022-09-06

Breaking Changes
  • fix: preserve moduleSideEffects when re-resolving files (#​1245)

v13.3.0

2022-05-02

Features
  • feat: support node: protocol (#​1124)

v13.2.2

2022-05-02

Bugfixes
  • fix: Respect if other plugins resolve the resolution to a different id (#​1181)
  • fix: Revert respect if other plugins resolve the resolution to a different id (ae59ceb)
  • fix: Respect if other plugins resolve the resolution to a different id (f8d4c44)

v13.2.1

2022-04-15

Bugfixes
  • fix: update side effects logic to be deep when glob doesn’t contain / (#​1148)

v13.2.0

2022-04-11

Features
  • feat: Add the ability to pass a function into resolveOnly (#​1152)

v13.1.3

2022-01-05

Bugfixes
  • fix: use correct version when published (#​1063)

v13.1.2

2021-12-31

Bugfixes
  • fix: forward meta-information from other plugins (#​1062)

v13.1.1

2021-12-13

Updates
  • test: add tests for mixing custom exportConditions with browser: true (#​1043)

v13.1.0

2021-12-13

Features
  • feat: expose plugin version (#​1050)

v13.0.6

2021-10-19

Bugfixes

v13.0.5

2021-09-21

Updates
  • docs: fix readme heading depth (#​999)

v13.0.4

2021-07-24

Bugfixes
  • fix: Fix bug where JS import was converted to a TS import, resulting in an error when using export maps (#​921)

v13.0.3

2021-07-24

Bugfixes
  • fix: handle browser-mapped paths correctly in nested contexts (#​920)

v13.0.2

2021-07-15

Bugfixes
  • fix: handle "package.json" being in path (#​927)

v13.0.1

2021-07-15

Updates
  • docs: Document how to get Node.js exports resolution (#​884)

v13.0.0

2021-05-04

Breaking Changes
  • fix!: mark module as external if resolved module is external (#​799)
Features
  • feat: Follow up to #​843, refining exports and browser field interaction (#​866)

v11.2.1

2021-03-26

Bugfixes
  • fix: fs.exists is incorrectly promisified (#​835)

v11.2.0

2021-02-14

Features
  • feat: add ignoreSideEffectsForRoot option (#​694)
Updates
  • chore: mark url as an external and throw on warning (#​783)
  • docs: clearer "Resolving Built-Ins" doc (#​782)

v11.1.1

2021-01-29

Bugfixes
  • fix: only log last resolve error (#​750)
Updates
  • docs: add clarification on the order of package entrypoints (#​768)

v11.1.0

2021-01-15

Features
  • feat: support pkg imports and export array (#​693)

v11.0.1

2020-12-14

Bugfixes
  • fix: export map specificity (#​675)
  • fix: add missing type import (#​668)
Updates
  • docs: corrected word "yse" to "use" (#​723)

v11.0.0

2020-11-30

Breaking Changes
  • refactor!: simplify builtins and remove customResolveOptions (#​656)
  • feat!: Mark built-ins as external (#​627)
  • feat!: support package entry points (#​540)
Bugfixes
  • fix: refactor handling builtins, do not log warning if no local version (#​637)
Updates
  • docs: fix import statements in examples in README.md (#​646)

v10.0.0

2020-10-27

Breaking Changes
  • fix!: resolve hash in path (#​588)
Bugfixes
  • fix: do not ignore exceptions (#​564)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/rollup-plugin-node-resolve-15.x branch from 7d01bef to a6d1b50 Compare August 17, 2023 03:16
@renovate
Copy link
Contributor Author

renovate bot commented Aug 17, 2023 •
edited

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @rollup/plugin-node-resolve@15.2.1
npm ERR! Found: rollup@2.1.0
npm ERR! node_modules/rollup
npm ERR!   dev rollup@"2.1.0" from the root project
npm ERR!   peerOptional rollup@"^1.20.0||^2.0.0||^3.0.0" from @rollup/plugin-json@6.0.0
npm ERR!   node_modules/@rollup/plugin-json
npm ERR!     dev @rollup/plugin-json@"6.0.0" from the root project
npm ERR!   3 more (@rollup/pluginutils, rollup-plugin-commonjs, rollup-plugin-terser)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional rollup@"^2.78.0||^3.0.0" from @rollup/plugin-node-resolve@15.2.1
npm ERR! node_modules/@rollup/plugin-node-resolve
npm ERR!   dev @rollup/plugin-node-resolve@"15.2.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: rollup@3.28.1
npm ERR! node_modules/rollup
npm ERR!   peerOptional rollup@"^2.78.0||^3.0.0" from @rollup/plugin-node-resolve@15.2.1
npm ERR!   node_modules/@rollup/plugin-node-resolve
npm ERR!     dev @rollup/plugin-node-resolve@"15.2.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/58765e/8a94c7/cache/others/npm/_logs/2023-08-22T07_58_59_553Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/58765e/8a94c7/cache/others/npm/_logs/2023-08-22T07_58_59_553Z-debug-0.log

@renovate renovate bot force-pushed the renovate/rollup-plugin-node-resolve-15.x branch from a6d1b50 to 4e19914 Compare August 22, 2023 07:59
@tinovyatkin tinovyatkin merged commit 9596931 into master Aug 23, 2023
0 of 5 checks passed
@tinovyatkin tinovyatkin deleted the renovate/rollup-plugin-node-resolve-15.x branch August 23, 2023 21:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@tinovyatkin