Meet the team
See all 1 on GitHub →
Commit activity
Last 12 weeks · 0 commits
Community health
2 of 6 standards met
50
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · 2 in progress · Last activity 11mo ago
See all on GitHub →
If I comment out , an error is reported: In other words, prevents valid error messages from being thrown, making the problem more difficult to troubleshoot. In addition to the useless error message mentioned above, it sometimes causes a Rust panic of or .
But after bundle into a single file through , the blocks of all imported submodules also enter the dist file and will be run. This is not expected behavior and causes surprises. The deno plugin should remove the block of non-entry modules, or possibly replace it with and discard the block via tree-shaking.
Recent fixes
There's automatic discovery of Deno config files for the loader, but I am unsure if this also supports workspaces. Because I have files in multiple levels, I am unsure if this plugin finds the root config file. Even with , there's no logging for helping me figure this out either. Currently when using the plugin, I am unsure if: Is the workspace loaded correctly? Is the lock-file being applied or not? Is and respected? Suggestion Many other Typescript plugins for bundlers or bundlers themselves, they often log the that was resolved and used.
When using the with , I get various different kinds of panics from Deno/Tokio when trying to bundle when the cache is missing a dependency. There seems to be some some race conditions, possibly related to workers, since I've seen three different kinds of errors so far. I don't know this issue should be here, or in , or in , but I've only been able to reproduce the issue by using the , so I thought this might be the best fit. Deno Panic 'tokio-runtime-worker' panic + Deno Panic 'tokio-runtime-worker' panic + [plugin deno-plugin] error Reproduction 1. Create an entrypoint 2. Create a file for bundling; must use as plugin option 3. Ensure that there is no installed in the deno cache (or clear via ) 4. Run the bundle file with or 5. Various errors should be produced Expected No panics, and errors reported from the plugin to tsdown. Actual Panic or hard to read plugin error. Not sure there's much added information by using this, as there seems to be some nested panic now that did not get the env-variable passed down, as I see another "Deno has panicked" message at the bottom with "re-run with the RUST_BACKTRACE=1 env var set". Error System () deno 2.3.7 (stable, release, x86_64-pc-windows-msvc) v8 13.7.152.6-rusty typescript 5.8.3
Structured data for AI agents
Repository: denoland/deno-rolldown-plugin. Description: Rolldown plugin for Deno code. Stars: 31, Forks: 2. Primary language: TypeScript. Languages: TypeScript (100%). License: MIT. Homepage: https://jsr.io/@deno/rolldown-plugin Latest release: 0.0.10 (11mo ago). Open PRs: 2, open issues: 3. Last activity: 11mo ago. Community health: 50%. Top contributors: dsherret.