chore: Ensure prettier is run on all files (#17497)

This simplifies our prettier setup to also run on e2e-tests, and aligns
the `fix:prettier` and `lint:prettier` targets (which were previously
not aligned).

Changes being done here:

1. Apply prettier to all e2e test apps normally (no special prettier
handling inside of the test apps)
2. Removed `.prettierrc.json` file, this was duplicated from the config
in the root package.json
3. Ensure prettier is applied to JSON files as well
4. Ensure prettier is applied to .astro files (needs astro plugin)

Author: mydea

.claude/settings.local.json

@@ -11,4 +11,4 @@
     ],
     "deny": []
   }
-}
+}

.prettierignore

@@ -1,3 +1,4 @@
 packages/browser/test/loader.js
 packages/replay-worker/examples/worker.min.js
 dev-packages/browser-integration-tests/fixtures
+**/test.ts-snapshots/**

.prettierrc.json

@@ -15,7 +15,6 @@
 
   We will follow up with docs how to set up the SDK soon.
   For now, If you're on SvelteKit version `2.31.0` or newer, you can easily opt into the new feature:
-
   1. Enable [experimental tracing and instrumentation support](https://svelte.dev/docs/kit/observability) in `svelte.config.js`:
   2. Move your `Sentry.init()` call from `src/hooks.server.(js|ts)` to the new `instrumentation.server.(js|ts)` file:
 
@@ -650,7 +649,6 @@ Work in this release was contributed by @0xbad0c0d3 and @alSergey. Thank you for
 - **feat(nuxt): Add Cloudflare Nitro plugin ([#15597](https://github.com/getsentry/sentry-javascript/pull/15597))**
 
   A Nitro plugin for `@sentry/nuxt` which initializes Sentry when deployed to Cloudflare (`cloudflare-pages` preset).
-
   1. Remove the previous server config file: `sentry.server.config.ts`
   2. Add a plugin in `server/plugins` (e.g. `server/plugins/sentry-cloudflare-setup.ts`)
   3. Add this code in your plugin file
@@ -1215,7 +1213,6 @@ This PR adds trace propagation to `@sentry/react-router` by providing utilities
 - **Logging Improvements**
 
   Sentry is adding support for [structured logging](https://github.com/getsentry/sentry-javascript/discussions/15916). In this release we've made a variety of improvements to logging functionality in the Sentry SDKs.
-
   - feat(node): Add server.address to nodejs logs ([#16006](https://github.com/getsentry/sentry-javascript/pull/16006))
   - feat(core): Add sdk name and version to logs ([#16005](https://github.com/getsentry/sentry-javascript/pull/16005))
   - feat(core): Add sentry origin attribute to console logs integration ([#15998](https://github.com/getsentry/sentry-javascript/pull/15998))
@@ -1264,7 +1261,6 @@ Work in this release was contributed by @Page- and @Fryuni. Thank you for your c
 ### Important Changes
 
 - **feat: Add support for logs**
-
   - feat(node): Add logging public APIs to Node SDKs ([#15764](https://github.com/getsentry/sentry-javascript/pull/15764))
   - feat(core): Add support for `beforeSendLog` ([#15814](https://github.com/getsentry/sentry-javascript/pull/15814))
   - feat(core): Add support for parameterizing logs ([#15812](https://github.com/getsentry/sentry-javascript/pull/15812))
@@ -1314,13 +1310,11 @@ Work in this release was contributed by @Page- and @Fryuni. Thank you for your c
   ```
 
   The result will be an object with the following properties:
-
   - `"no-client-active"`: There was no active client when the function was called. This possibly means that the SDK was not initialized yet.
   - `"sentry-unreachable"`: The Sentry SaaS servers were not reachable. This likely means that there is an ad blocker active on the page or that there are other connection issues.
   - `undefined`: The SDK is working as expected.
 
 - **SDK Tracing Performance Improvements for Node SDKs**
-
   - feat: Stop using `dropUndefinedKeys` ([#15796](https://github.com/getsentry/sentry-javascript/pull/15796))
   - feat(node): Only add span listeners for instrumentation when used ([#15802](https://github.com/getsentry/sentry-javascript/pull/15802))
   - ref: Avoid `dropUndefinedKeys` for `spanToJSON` calls ([#15792](https://github.com/getsentry/sentry-javascript/pull/15792))

CHANGELOG.md

@@ -95,7 +95,6 @@ occur while writing tests for Sentry Browser SDK.
 
   Before running, a page for each test case is built under the case folder inside `dist`. If a page build is failed,
   it's recommended to check:
-
   - If both default `template.hbs` and `init.js` are defined for the test group.
   - If a `subject.js` is defined for the test case.
   - If either of `init.js` or `subject.js` contain non-browser code.

dev-packages/browser-integration-tests/README.md

@@ -26,16 +26,15 @@ sentryTest('allows to ignore mutations via `ignoreMutations` option', async ({ g
   const requests = await requestsPromise;
 
   // All transform mutatinos are ignored and not captured
-  const transformMutations = requests.replayRecordingSnapshots.filter(
-    item =>
-      (item.data as mutationData)?.attributes?.some(
-        attr => attr.attributes['style'] && attr.attributes['class'] !== 'moved',
-      ),
+  const transformMutations = requests.replayRecordingSnapshots.filter(item =>
+    (item.data as mutationData)?.attributes?.some(
+      attr => attr.attributes['style'] && attr.attributes['class'] !== 'moved',
+    ),
   );
 
   // Should capture the final class mutation
-  const classMutations = requests.replayRecordingSnapshots.filter(
-    item => (item.data as mutationData)?.attributes?.some(attr => attr.attributes['class']),
+  const classMutations = requests.replayRecordingSnapshots.filter(item =>
+    (item.data as mutationData)?.attributes?.some(attr => attr.attributes['class']),
   );
 
   expect(transformMutations).toEqual([]);

dev-packages/browser-integration-tests/suites/replay/ignoreMutations/test.ts

@@ -142,13 +142,10 @@ export const countEnvelopes = async (
 
     page.on('request', requestHandler);
 
-    setTimeout(
-      () => {
-        page.off('request', requestHandler);
-        resolve(reqCount);
-      },
-      options?.timeout || 1000,
-    );
+    setTimeout(() => {
+      page.off('request', requestHandler);
+      resolve(reqCount);
+    }, options?.timeout || 1000);
   });
 
   if (options?.url) {

dev-packages/browser-integration-tests/utils/helpers.ts

@@ -7,6 +7,6 @@
     // Although this seems wrong to include `DOM` here, it's necessary to make
     // global fetch available in tests in lower Node versions.
     "lib": ["ES2020"],
-    "esModuleInterop": true,
+    "esModuleInterop": true
   }
 }

dev-packages/cloudflare-integration-tests/tsconfig.json

@@ -81,11 +81,11 @@ for it to work with both regular and prerelease versions:
   "scripts": {
     "test": "echo \"Hello world!\"",
     "test:build": "pnpm install",
-    "test:assert": "pnpm test"
+    "test:assert": "pnpm test",
   },
   "dependencies": {
-    "@sentry/node": "latest || *"
-  }
+    "@sentry/node": "latest || *",
+  },
 }
 ```
 

dev-packages/e2e-tests/README.md

@@ -16,17 +16,10 @@
             "outputPath": "dist/angular-17",
             "index": "src/index.html",
             "browser": "src/main.ts",
-            "polyfills": [
-              "zone.js"
-            ],
+            "polyfills": ["zone.js"],
             "tsConfig": "tsconfig.app.json",
-            "assets": [
-              "src/favicon.ico",
-              "src/assets"
-            ],
-            "styles": [
-              "src/styles.css"
-            ],
+            "assets": ["src/favicon.ico", "src/assets"],
+            "styles": ["src/styles.css"],
             "scripts": []
           },
           "configurations": {
@@ -74,18 +67,10 @@
         "test": {
           "builder": "@angular-devkit/build-angular:karma",
           "options": {
-            "polyfills": [
-              "zone.js",
-              "zone.js/testing"
-            ],
+            "polyfills": ["zone.js", "zone.js/testing"],
             "tsConfig": "tsconfig.spec.json",
-            "assets": [
-              "src/favicon.ico",
-              "src/assets"
-            ],
-            "styles": [
-              "src/styles.css"
-            ],
+            "assets": ["src/favicon.ico", "src/assets"],
+            "styles": ["src/styles.css"],
             "scripts": []
           }
         }