-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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.
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
🐛 BUG: vite.build.sourcemap does not generate sourcemaps for client-side components on build #3970
Comments
On a closer look there do seem to be some sourcemaps in (also maybe only for markdown pages? Unsure) |
Ooh very strange! Thanks for opening an issue, I know digging into sourcemaps is definitely on our list. This would be great to fix. |
Happening in dev as well in 1.0rc3:
|
@natemoo-re I'm going to hand this one over to @bluwy. |
Gimme |
This would be a good one to create a test for. |
Still happening with 1.0.0.
|
What version of
astro
are you using?1.0.0-beta.72
Are you using an SSR adapter? If so, which one?
none
What package manager are you using?
pnpm
What operating system are you using?
Linux
Describe the Bug
Sourcemaps are useful for debugging components while developing an application. But there are also tools (Ex. Sentry), that can use the sourcemaps in production to get a similar experience with in-the-wild bugs.
This functionality is currently unavailable however, as astro fails to generate soucemaps on build
The bug
vite.build.sourcemap
inastro.config.mjs
to trueExpected: A sourcemap file (
*.js.map
) for each client-side script in./dist
, as well as the script itself referencing the sourcemap as per viteActual: an almost empty
entry.mjs.map
with no modifications to other filesThis was also in the build logs:
Link to Minimal Reproducible Example
https://github.com/withastro/astro/tree/latest/examples/framework-svelte
Participation
The text was updated successfully, but these errors were encountered: