When sentry.client.config.js is present, Astro builds fail.

[aozou99]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Self-hosted/on-premise

Which SDK are you using?

@sentry/astro

SDK Version

10.9.0

Framework Version

astro@5.13.5 @astrojs/node9.4.3

Link to Sentry event

No response

Reproduction Example/SDK Setup

astro.config.mjs

// @ts-check
import { defineConfig } from "astro/config";
import node from "@astrojs/node";

import sentry from "@sentry/astro";

// https://astro.build/config
export default defineConfig({
  output: "server",
  adapter: node({
    mode: "standalone",
  }),
  integrations: [
    sentry({
      sourceMapsUploadOptions: {
        project: __YOUR_PROJECT__,
        org: __YOUR_ORG__",
        authToken: __YOUR_TOKEN__
      },
    }),
  ],
  vite: {
    build: {
      rollupOptions: {
        external: ["fsevents"],  //  Added fsevents because an error occurred when build.
      },
    },
  },
});

sentry.client.config.js

import * as Sentry from "@sentry/astro";

Sentry.init({
  dsn: __YOUE_DSN__,

  integrations: [],
});

Steps to Reproduce

1. npm create astro@latest
2. npx astro add @sentry/astro
3. npm i @astrojs/node
4. add sentry.client.config.js & edit astro.config.mjs
5. npm run build

Expected Result

Build success

Actual Result

05:35:43 [ERROR] [vite] ✗ Build failed in 3.13s
node_modules/rollup/dist/es/shared/parseAst.js (11:27): "basename" is not exported by "__vite-browser-external", imported by "node_modules/rollup/dist/es/shared/parseAst.js".
file: /workspaces/test/node_modules/rollup/dist/es/shared/parseAst.js:11:27

 9: */
10: import { parse, parseAsync } from '../../native.js';
11: import { resolve, dirname, basename, extname } from 'node:path';
                               ^
12: 
13: // This file is generated by scripts/generate-node-types.js.

Deleting sentry.client.config.js allows the build to succeed normally.
However, client-side errors like the one in the sample did not appear to be sent to Sentry.

src/pages/index.astro

<button onclick="throw new Error('This is a test error')">Throw test error</button>

[linear]

JS-905 When sentry.client.config.js is present, Astro builds fail.

[Lms24]

Hey @aozou99 thanks for writing in! I tried reproducing this but unfortunately didn't get the error. Can you take a look at https://github.com/Lms24/gh-sentry-javascript-17533-astro-client-config and let me know what to change? Alternatively, please feel free to provide your own minimal reproduction. Thanks!

[aozou99]

@Lms24 Thank you for reviewing this.
It was extremely helpful that you also deployed the repository to reproduce the issue.
While reviewing the diff, I identified the cause.
In my sentry.client.config.js, I had written the following to read the DSN from environment variables using loadEnv.
In the issue, I omitted this to keep things simple, which caused unnecessary confusion. My apologies.

sentry.client.config.js

import * as Sentry from "@sentry/astro";
import { loadEnv } from "vite";

const { SENTRY_DSN } = loadEnv(process.env.NODE_ENV || "", process.cwd(), "");
Sentry.init({
  dsn: SENTRY_DSN,

  integrations: [],
});

Thanks to this, I realized that sentry.client.config.js likely has a constraint preventing it from using server-side modules.
Ideally, it would be great if loadEnv could be used in sentry.client.config.js too. Is this difficult to implement?