We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Hello! I encountered a problem when one of the entry points contains an absolute path to the cdn.
Example:
// index.js import { useState } from "./shared-react-package.js";
// shared-react-package.js export * from "https://esm.sh/[email protected]/es2022/react.development.mjs"; export { default } from "https://esm.sh/[email protected]/es2022/react.development.mjs";
Run esbuild index.js shared-react.package.js --bundle --outdir=out --conditions=development --format=esm --splitting
esbuild index.js shared-react.package.js --bundle --outdir=out --conditions=development --format=esm --splitting
My case:
Vite starts the optimizer with deps:
Can I hope that this will work in future versions?
node: 20.17.0 esbuild: 0.25.1 vite: 6.2.2
The text was updated successfully, but these errors were encountered:
Just want to add the playground link where rollup works fine.
Sorry, something went wrong.
No branches or pull requests
Hello! I encountered a problem when one of the entry points contains an absolute path to the cdn.
Example:
Run
esbuild index.js shared-react.package.js --bundle --outdir=out --conditions=development --format=esm --splitting
My case:
Vite starts the optimizer with deps:
Can I hope that this will work in future versions?
node: 20.17.0
esbuild: 0.25.1
vite: 6.2.2
The text was updated successfully, but these errors were encountered: