一笑
一笑
This issue shouldn’t exist in Rollup 4.46.1. Could you double-check which version of Rollup you had installed when you encountered the problem?
In your reproduction link, the compiled code produces the same result as the original source. I’m curious to see the source code that led to the compiled version which caused...
You can use the [resolveimportmeta](https://rollupjs.org/plugin-development/#resolveimportmeta) hook to replace `import.meta.url` with your desired code snippet.
Oh, I misunderstood before. I get it now—if an async function doesn’t have an `await`, its execution behaves like synchronous code. Thanks for reminding me!
After thinking it through, it seems difficult to replace an awaiting import expression with `0`. First, the `AwaitExpression`’s `hasEffects` function has to return `true`, otherwise, the `render` function won't run,...
@LongTengDao Hi, do you think this PR #6120 could solve your scenario? You can set `moduleSideEffects` to indicate that this `import()` is pure, and if the exports are not used,...
Uh, I checked the reproduction link but didn’t see the error you mentioned.
Got it — I can see the error under `preview` now. And yes, the dev mode looks fine.
I had a look at this just now. The issue is that there is a circular dependency between the chunks. As a workaround, you can try including the `scheduler` package...
`scheduler` is actually an independent package. In your `vite.config.ts`, you didn’t include `scheduler` in the `react` chunk, so it ends up being bundled into the `vendor` chunk instead.