chore(deps): update dependency @rollup/plugin-node-resolve to v15

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@rollup/plugin-node-resolve (source)	8.4.0 -> 15.3.0

---

Release Notes

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

v15.3.0

2024-09-23

Features

• feat: allow preferBuiltins to be a function (#​1694)

v15.2.4

2024-09-22

Updates

• chore: remove is-builtin-module (#​1735)

v15.2.3

Compare Source

2023-10-08

Bugfixes

• fix: modulePaths default is not set #​1534

v15.2.2

Compare Source

2023-10-05

Bugfixes

• fix: ensure rollup 4 compatibility #​1595

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

• fix: prepare for Rollup 3 #​1288

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

• fix: pass on isEntry flag (#​1016)

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)

v9.0.0

2020-08-13

Breaking Changes

• chore: update dependencies (e632469)

Updates

• refactor: remove deep-freeze from dependencies (#​529)
• chore: clean up changelog (84dfddb)

---

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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ 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: sapper/package-lock.json

ERROR: npm v10.2.0 is known not to run on Node.js v14.21.3.  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.

ERROR:
/opt/containerbase/tools/npm/10.2.0/node_modules/npm/node_modules/@npmcli/agent/lib/agents.js:105
    options.lookup ??= this.#options.lookup
                   ^^^

SyntaxError: Unexpected token '??='
    at wrapSafe (internal/modules/cjs/loader.js:1029:16)
    at Module._compile (internal/modules/cjs/loader.js:1078:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)
    at Module.load (internal/modules/cjs/loader.js:979:32)
    at Function.Module._load (internal/modules/cjs/loader.js:819:12)
    at Module.require (internal/modules/cjs/loader.js:1003:19)
    at require (internal/modules/cjs/helpers.js:107:18)
    at Object.<anonymous> (/opt/containerbase/tools/npm/10.2.0/node_modules/npm/node_modules/@npmcli/agent/lib/index.js:7:15)
    at Module._compile (internal/modules/cjs/loader.js:1114:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)
ERROR: npm v10.2.0 is known not to run on Node.js v14.21.3.  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.

ERROR:
/opt/containerbase/tools/npm/10.2.0/node_modules/npm/node_modules/@npmcli/agent/lib/agents.js:105
    options.lookup ??= this.#options.lookup
                   ^^^

SyntaxError: Unexpected token '??='
    at wrapSafe (internal/modules/cjs/loader.js:1029:16)
    at Module._compile (internal/modules/cjs/loader.js:1078:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)
    at Module.load (internal/modules/cjs/loader.js:979:32)
    at Function.Module._load (internal/modules/cjs/loader.js:819:12)
    at Module.require (internal/modules/cjs/loader.js:1003:19)
    at require (internal/modules/cjs/helpers.js:107:18)
    at Object.<anonymous> (/opt/containerbase/tools/npm/10.2.0/node_modules/npm/node_modules/@npmcli/agent/lib/index.js:7:15)
    at Module._compile (internal/modules/cjs/loader.js:1114:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)