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

chore(deps): update npm-rolldown (major) #1616

Closed
wants to merge 1 commit into from
Closed

chore(deps): update npm-rolldown (major) #1616

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 14, 2024 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) 20.14.13 -> 22.0.0 age adoption passing confidence
glob ^10.4.1 -> ^11.0.0 age adoption passing confidence
vitest (source) ^1.6.0 -> ^2.0.0 age adoption passing confidence
why-is-node-running ^2.2.2 -> ^3.0.0 age adoption passing confidence

Release Notes

isaacs/node-glob (glob)

v11.0.0

Compare Source

vitest-dev/vitest (vitest)

v2.0.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.0.2

Compare Source

v2.0.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.0

Compare Source

Vitest 2.0 is here! This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.

🚨 Breaking Changes
🚀 Features
🐞 Bug Fixes
View changes on GitHub
mafintosh/why-is-node-running (why-is-node-running)

v3.2.0

Compare Source

Notable Changes

Relative file paths

The file paths shown in the output are now relative to the current working directory, if a path is outside of the current working directory the full absolute path will be used instead.

Before

There are 4 handle(s) keeping the process running

### Timeout
/path/to/project/example.js:6  - setInterval(() => {}, 1000)
/path/to/project/example.js:10 - startServer()

### TCPSERVERWRAP
/path/to/project/example.js:7  - server.listen(0)
/path/to/project/example.js:10 - startServer()

### Timeout
/path/to/project/example.js:6  - setInterval(() => {}, 1000)
/path/to/project/example.js:11 - startServer()

### TCPSERVERWRAP
/path/to/project/example.js:7  - server.listen(0)
/path/to/project/example.js:11 - startServer()

After

There are 4 handle(s) keeping the process running
### Timeout
example.js:6  - setInterval(() => {}, 1000)
example.js:10 - startServer()
### TCPSERVERWRAP
example.js:7  - server.listen(0)
example.js:10 - startServer()
### Timeout
example.js:6  - setInterval(() => {}, 1000)
example.js:11 - startServer()
### TCPSERVERWRAP
example.js:7  - server.listen(0)
example.js:11 - startServer()
No more dependencies

This version of why-is-node-running removes all of it's additional dependencies, resulting in a smaller overall package size.

What's Changed

Full Changelog: mafintosh/why-is-node-running@v3.1.0...v3.2.0

v3.1.0

Compare Source

What's Changed

Full Changelog: mafintosh/why-is-node-running@v3.0.0...v3.1.0

v3.0.0

Compare Source

What's Changed

Breaking Changes

This release raises the required Node.js version to 20.11 or higher, and introduces support for standardized JavaScript modules. This makes the package incompatible with CommonJS based environments and is thus a breaking change. If you want to use this version the following changes should be made:

Use JavaScript modules instead of CommonJS

-const why = require('why-is-node-running')
+import why from 'why-is-node-running'

Use --import instead of --require

-node --require why-is-node-running/include /path/to/some/file.js
+node --import why-is-node-running/include /path/to/some/file.js

Full Changelog: mafintosh/why-is-node-running@v2.3.0...v3.0.0

Configuration

📅 Schedule: Branch creation - "before 10am on monday" in timezone Asia/Shanghai, 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, check this box

This PR was generated by Mend Renovate. View the repository job log.

@netlify Netlify
Copy link

netlify bot commented Jul 14, 2024 •
edited
Loading

✅ Deploy Preview for rolldown-rs canceled.

Name Link
🔨 Latest commit cfea6c1
🔍 Latest deploy log https://app.netlify.com/sites/rolldown-rs/deploys/66a92fa32a332e0008739dc1

@renovate renovate bot force-pushed the renovate/major-npm-rolldown branch from ea1fc79 to 096cc1f Compare July 15, 2024 13:11
@IWANABETHATGUY IWANABETHATGUY force-pushed the renovate/major-npm-rolldown branch from 096cc1f to ae9b070 Compare July 17, 2024 07:31
@hi-ogawa
Copy link
Member

I'm checking Vitest v2 failure here and this might be a same failure as the one I found in vite-plugin-react repo. I reported an issue upstream vitest-dev/vitest#6152

Importing a generated file (in this case import "./dist/main") is failing since V2.

rolldown/packages/rolldown/tests/fixtures/builtin-plugin/glob-import/basic/assert.mjs

Line 3 in 65b119a

import { modules1, modules2 } from './dist/main' 

Caused by: Error: Failed to load url ./dist/main (resolved id: ./dist/main) in /Users/runner/work/rolldown/rolldown/packages/rolldown/tests/fixtures/builtin-plugin/glob-import/basic/assert.mjs. Does the file exist?

@renovate renovate bot force-pushed the renovate/major-npm-rolldown branch 2 times, most recently from 673df82 to 0c08823 Compare July 28, 2024 10:15
@renovate renovate bot force-pushed the renovate/major-npm-rolldown branch from 0c08823 to 4e99fd0 Compare July 28, 2024 17:49
@renovate renovate bot force-pushed the renovate/major-npm-rolldown branch from 4e99fd0 to cfea6c1 Compare July 30, 2024 18:23
@hyf0 hyf0 closed this Jul 31, 2024
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
needs-triage
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@hi-ogawa @hyf0