Skip to content

fix(node/plugin): ensure order for generateBundle and writeBundle hooks#1913

Merged
underfin merged 1 commit intomainfrom
fix-generate-bundle
Aug 9, 2024
Merged

fix(node/plugin): ensure order for generateBundle and writeBundle hooks#1913
underfin merged 1 commit intomainfrom
fix-generate-bundle

Conversation

@underfin
Copy link
Contributor

@underfin underfin commented Aug 9, 2024

Description

@netlify
Copy link

netlify bot commented Aug 9, 2024

Deploy Preview for rolldown-rs canceled.

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

@hyf0 hyf0 changed the title fix: specify order for generateBundle and writeBundle hooks fix(node/plugin): ensure order for generateBundle and writeBundle hooks Aug 9, 2024
@underfin underfin added this pull request to the merge queue Aug 9, 2024
Merged via the queue into main with commit b7e1d90 Aug 9, 2024
@underfin underfin deleted the fix-generate-bundle branch August 9, 2024 07:15
github-merge-queue bot pushed a commit that referenced this pull request Jan 29, 2025
### Description

I added a fake "deprecated" type to reduce a churn due to ecosystem
failing by ts error (see
https://github.com/vitejs/vite-ecosystem-ci/blob/rolldown-vite/README-temp.md
and also my plugin hit by this too
hi-ogawa/vite-plugins#673).

As I wrote in
#3337 (comment),
Rolldown's plugin hook always works same as rollup's `sequential: true`
and this behavior is likely good for the ecosystem since people mostly
needed `sequential: true` to avoid running `writeBundle` hooks in
parallel on rollup.

I think the test added in #1913
already verifies such sequential behavior.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants