@cypress/vite-dev-server 5.2.0 → 5.2.1

package/dist/plugins/sourcemap.js

@@ -10,26 +10,31 @@ const CypressSourcemap = (options, vite) => {
         enforce: 'post',
         transform(code, id, options) {
             try {
-                if (/\.js$/i.test(id) && !/\/\/# sourceMappingURL=/i.test(code)) {
+                // Remove query parameters from the id. This is necessary because some files
+                // have a cache buster query parameter (e.g. `?v=12345`)
+                const queryParameterLessId = id.split('?')[0];
+                // Check if the file has a JavaScript extension and does not have an inlined sourcemap
+                if (/\.(js|jsx|ts|tsx|vue|svelte|mjs|cjs)$/i.test(queryParameterLessId) && !/\/\/# sourceMappingURL=data/i.test(code)) {
                     /*
-                    The Vite dev server and plugins automatically generate sourcemaps for most files, but they are
-                    only included in the served files if any transpilation actually occurred (JSX, TS, etc). This
-                    means that files that are "pure" JS won't include sourcemaps, so JS spec files that don't require
-                    transpilation won't get code frames in the runner.
-          
-                    A sourcemap for these files is generated (just not served) which is in effect an "identity"
-                    sourcemap mapping 1-to-1 to the output file. We can grab this and pass it along as a sourcemap
-                    we want Vite to embed into the output, giving Cypress a sourcemap to use for codeFrame lookups.
-                    @see https://rollupjs.org/guide/en/#thisgetcombinedsourcemap
-          
-                    We utilize a 'post' plugin here and manually append the sourcemap content to the code. We *should*
+                    The Vite dev server and plugins automatically generate sourcemaps for most files, but there are
+                    some files that don't have sourcemaps generated for them or are not inlined. We utilize a 'post' plugin
+                    here and manually append the sourcemap content to the code in these cases. We *should*
                     be able to pass the sourcemap along using the `map` attribute in the return value, but Babel-based
                     plugins don't work with this which causes sourcemaps to break for files that go through common
                     plugins like `@vitejs/plugin-react`. By manually appending the sourcemap at this point in time
                     Babel-transformed files end up with correct sourcemaps.
                     */
                     const sourcemap = this.getCombinedSourcemap();
-                    code += `\n//# sourceMappingURL=${sourcemap.toUrl()}`;
+                    const sourcemapUrl = sourcemap.toUrl();
+                    if (/\/\/# sourceMappingURL=/i.test(code)) {
+                        // If the code already has a sourceMappingURL, it is not an inlined sourcemap
+                        // and we should replace it with the new sourcemap
+                        code = code.replace(/\/\/# sourceMappingURL=(.*)$/m, `//# sourceMappingURL=${sourcemapUrl}`);
+                    }
+                    else {
+                        // If the code does not have a sourceMappingURL, we should append the new sourcemap
+                        code += `\n//# sourceMappingURL=${sourcemapUrl}`;
+                    }
                     return {
                         code,
                         map: { mappings: '' },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cypress/vite-dev-server",
-  "version": "5.2.0",
+  "version": "5.2.1",
   "description": "Launches Vite Dev Server for Component Testing",
   "main": "index.js",
   "scripts": {