issue with using CommonJS modules in "svelte/kit build" #928

henryennis · 2021-04-08T10:05:03Z

App runs normally while running in dev mode, error is thrown on build

svelte.config.cjs

Note the package causing this issue is set to be converted to esm as of the:

optimizeDeps: {
				include: ['carbon-components-svelte', 'clipboard-copy']
		        },

svelte.config.cjs

const sveltePreprocess = require('svelte-preprocess');
const node = require('@sveltejs/adapter-node');
const pkg = require('./package.json');

/** @type {import('@sveltejs/kit').Config} */
module.exports = {
	// Consult https://github.com/sveltejs/svelte-preprocess
	// for more information about preprocessors
	preprocess: sveltePreprocess(),
	kit: {
		// By default, `npm run build` will create a standard Node app.
		// You can create optimized builds for different platforms by
		// specifying a different adapter
		adapter: node(),
		ssr: false,
		// hydrate the <div id="svelte"> element in src/app.html
		target: '#svelte',

		vite: {
			// optimizeDeps: {
			// 	include: ['carbon-components-svelte', 'clipboard-copy']
			//   },
			ssr: {
				noExternal: Object.keys(pkg.dependencies || {})
			},
			plugins: [
				require('vite-plugin-windicss').default()
			  ]
		}
	}
};

importing modules from a commonJS package "carbon-components-svelte" like so:

index.svelte

<script>
  import {
    FluidForm,
    TextInput,
    PasswordInput, Tile
  } from "carbon-components-svelte";
import ButtonFullBleed from "../components/buttons/buttonFullBleed.svelte"
</script>

error

PS C:\Users\henry\sveltekit-dashboard> npm run build

> sveltekit-dashboard@0.0.1 build C:\Users\henry\sveltekit-dashboard
> svelte-kit build

vite v2.1.5 building for production...
✓ 320 modules transformed.
.svelte/output/client/_app/manifest.json                            0.67kb
.svelte/output/client/_app/chunks/index-4d122fc8.js                 5.48kb / brotli: 2.12kb
.svelte/output/client/_app/assets/pages\index.svelte-802f02f9.css   4.19kb / brotli: 0.85kb
.svelte/output/client/_app/start-fbcbe901.js                        15.83kb / brotli: 5.41kb
.svelte/output/client/_app/pages\index.svelte-97280b82.js           59.90kb / brotli: 15.52kb
.svelte/output/client/_app/assets/start-9caedf08.css                459.55kb / brotli: 37.33kb
vite v2.1.5 building SSR bundle for production...
✓ 17 modules transformed.
.svelte/output/server/app.js   544.67kb

Run npm start to try your app locally.

> Using @sveltejs/adapter-node
> Named export 'FluidForm' not found. The requested module 'carbon-components-svelte' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'carbon-components-svelte';
const {FluidForm} = pkg;

file:///C:/Users/henry/sveltekit-dashboard/.svelte/output/server/app.js:8
import {FluidForm} from "carbon-components-svelte";
SyntaxError: Named export 'FluidForm' not found. The requested module 'carbon-components-svelte' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'carbon-components-svelte';
const {FluidForm} = pkg;

    at ModuleJob._instantiate (internal/modules/esm/module_job.js:98:21)
    at async ModuleJob.run (internal/modules/esm/module_job.js:143:5)
    at async Loader.import (internal/modules/esm/loader.js:165:24)
    at async prerender (file:///C:/Users/henry/sveltekit-dashboard/node_modules/@sveltejs/kit/dist/chunks/index6.js:513:14)
    at async AdapterUtils.prerender (file:///C:/Users/henry/sveltekit-dashboard/node_modules/@sveltejs/kit/dist/chunks/index6.js:745:4)
    at async adapt (C:\Users\henry\sveltekit-dashboard\node_modules\@sveltejs\adapter-node\index.js:26:4)
    at async adapt (file:///C:/Users/henry/sveltekit-dashboard/node_modules/@sveltejs/kit/dist/chunks/index6.js:767:2)
    at async file:///C:/Users/henry/sveltekit-dashboard/node_modules/@sveltejs/kit/dist/cli.js:633:5

Note that:

The same issue happens when a Svelte component that imports a CommonJS module is imported in to a vanilla JS Vite project.

You can see the issue for yourselves by importing and instantiating the svelte-nano-donate component at this commit: small-tech/svelte-nano-donate@0d7bcf9 (works, QRious library is inlined) and the one before it (doesn’t work, QRious library is imported from node modules). Note that the second one will also work if you npm install the component via a local file path instead of from npm (I thought everything was fine until I tried to install the component in a Vite/SvelteKit project via npm).
(I’m going to go check on the Vite project to see if there are any related issues as we cannot be the first ones to get bitten by this.)

Credit: aral

other information
Node version: v14.15.0
OS: windows 10 10.0, build 19041

The text was updated successfully, but these errors were encountered:

aral · 2021-04-08T14:20:46Z

Seeing the same thing on build. Also seems to manifest as a 500 import not found: default error on npm run dev if a svelte component that uses a CommonJS module is installed from npm (works correctly if installed via a local file reference). Happy to open a separate issue for that but it feels like they’re the same one.

henryennis · 2021-04-08T15:05:16Z

Seeing the same thing on build. Also seems to manifest as a 500 import not found: default error on npm run dev if a svelte component that uses a CommonJS module is installed from npm (works correctly if installed via a local file reference). Happy to open a separate issue for that but it feels like they’re the same one.

I will adapt the post accordingly

aral · 2021-04-09T13:27:25Z

I will adapt the post accordingly

Note that:

The same issue happens when a Svelte component that imports a CommonJS module is imported in to a vanilla JS Vite project.
You can see the issue for yourselves by importing and instantiating the svelte-nano-donate component at this commit: small-tech/svelte-nano-donate@0d7bcf9 (works, QRious library is inlined) and the one before it (doesn’t work, QRious library is imported from node modules). Note that the second one will also work if you npm install the component via a local file path instead of from npm (I thought everything was fine until I tried to install the component in a Vite/SvelteKit project via npm).

(I’m going to go check on the Vite project to see if there are any related issues as we cannot be the first ones to get bitten by this.)

benmccann · 2021-04-09T17:31:32Z

I would suggest trying all the tips in https://github.com/sveltejs/kit/blob/master/documentation/faq/70-packages.md as a first step

Unfortunately, CommonJS is somewhat of a known pain point with Vite at the moment: vitejs/vite#2579

aral · 2021-04-09T21:35:25Z

@benmccann That’s hugely useful, thank you.

tolu · 2021-04-11T14:48:19Z

Just had the same issue and weirdly this solution from layercake issue tracker 👇 worked for me (but with @sanity/client dependency that needs prebundling)

Move vite config to own file vite.config.cjs so that

// vite.config.cjs
const pkg = require('./package.json');

/** @type {import('vite').UserConfig} */
export default {
  ssr: {
    noExternal: Object.keys(pkg.dependencies || {})
  },
};

// svelte.config.cjs
const sveltePreprocess = require('svelte-preprocess');
const node = require('@sveltejs/adapter-node');

/** @type {import('@sveltejs/kit').Config} */
module.exports = {
  preprocess: sveltePreprocess(),
  kit: {
    adapter: node(),
    target: '#svelte',

    // vite: {
    /* moved to vite.config.cjs */
    // }
  }
};

henryennis · 2021-04-11T14:52:53Z

weirdly this solution from layercake issue tracker 👇 worked for me (with @sanity/client dependency)

Move vite config to own file vite.config.cjs so that
// vite.config.cjs

const pkg = require('./package.json');



/** @type {import('vite').UserConfig} */

export default {

  ssr: {

    noExternal: Object.keys(pkg.dependencies || {})

  },

};

Are u saying to seperate vite config from svelte config cjs?

tolu · 2021-04-11T14:54:45Z

Are u saying to seperate vite config from svelte config cjs?

Yes, at least that worked for me 👍 I'll update my original comment to be more clear!

RemyDekor · 2021-04-16T15:33:39Z

I'm not sure I understand how noExternal is supposed to work, but just removing the vite config from the svelte.config.cjs worked for me

benmccann · 2021-04-22T06:03:18Z

The original issue description referred to carbon-components-svelte. For that library, I'm going to close this in favor of vitejs/vite#3024

For other libraries, the couple I tested seem to have been fixed by removing noExternal from the default template

If people are still having issues, please file a new issue with the specific library you're using and steps to reproduce or a repo that reproduces the issue

sjmcdowall · 2021-04-25T21:04:36Z

@benmccann -- Sorry to post to a closed issue -- but I have no idea if this is related or not at all . I am trying to use Antony's svelte-mapbox in my new Sveltekit app -- and as soon as I uncomment out the import Map statement -- I am getting a 500 error in the browser --

The requested module '/node_modules/fastq/queue.js?v=0e439b33' does not provide an export named 'default'

SyntaxError: The requested module '/node_modules/fastq/queue.js?v=0e439b33' does not provide an export named 'default'

Is this similar or different than this issue? I tried the vite noExternal thing above but that didn't change anything ... TIA!

/Steve

benmccann · 2021-04-26T04:39:42Z

@sjmcdowall there's an issue over in that repo that describes how to use it with SvelteKit: beyonk-group/svelte-mapbox#44

sjmcdowall · 2021-04-26T12:35:41Z

@benmccann -- Thank you! Sort of embarrassed I didn't see that myself. Cheers!

ecstrema · 2021-05-15T02:18:44Z

For the original issue, it can be resolved (partly) by using the carbon's import preprocessor, since it avoids going through index.js

This reverts commit 83d23a5.

* 👷 Switch to ESM build * 🔧 Use `module` instead of `main` config fields * 📌 Reinstall sk-auth * 🏷️ Fix type errors * 🔧 Create separate Vite config JS according to sveltejs/kit#928 * Revert "🔧 Create separate Vite config JS according to sveltejs/kit#928" This reverts commit 83d23a5. * ➕ Add `build-esm` as dev and peer dependency * 👷 Compile CJS module * 📌 Reinstall deps * 🔧 Switch to ESM build * Revert "🔧 Switch to ESM build" This reverts commit c908a57. * 🔧 Use `main` instead of `module` in `package.json`

praveenkpatare · 2021-08-11T23:21:19Z

Facing the same issue with jsonwebtoken library.. here is the screnshot of the error --

benmccann · 2021-08-12T00:02:25Z

We'll work on improved CJS support for Vite. But in the meantime see auth0/node-jsonwebtoken#785 auth0/node-jsonwebtoken#655 to improve that library

Marcosaurios · 2021-10-12T10:44:27Z

Any news about this? I am using latest adapter-static and facing the same issue, but in this case with style-value-types dependency (used in svelte-motion)...

> Using @sveltejs/adapter-static
> Named export 'px' not found. The requested module 'style-value-types' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'style-value-types';
const { number, px, degrees, scale, alpha, progressPercentage, complex, color, filter, percent, vw, vh } = pkg;

Edit:
Apparently adding the failing dependencies to SSR noExternal property of vite config, make it work, as @benmccann said before:

Here's an issue about chart.js: chartjs/Chart.js#9436

In the svelte.config.js:

const config = {
 kit: {
  vite: {
   ssr: {
    noExternal: ['style-value-types', 'popmotion', 'framesync']
   }
  }
 }
}

benmccann · 2021-10-12T19:52:31Z

That library is using an old version of style-value-types. Here's a PR to upgrade it: micha-lmxt/svelte-motion#10. I didn't test if it solves the issue you're having, but it's possible it does since it updates the exports map

Marcosaurios · 2021-10-12T20:26:09Z

@benmccann thank you so much for that! 👏✌️

see sveltejs/kit#928 ``` Named export 'faAsterisk' not found. The requested module '@fortawesome/free-solid-svg-icons' is a CommonJS module, which may not support all module.exports as named exports. CommonJS modules can always be imported via the default export, for example using: import pkg from '@fortawesome/free-solid-svg-icons'; const { faArrowLeft, faArrowRight, faAsterisk, faArrowRotateLeft, faFolderPlus, faEllipsis } = pkg; ```

ogrotten · 2021-12-20T18:20:55Z

Edit:
Apparently adding the failing dependencies to SSR noExternal property of vite config, make it work, as @benmccann said before:

This is the solution that worked for me.

ssr: {
	noExternal: ["svelte-hero-icons", '@googlemaps/js-api-loader'],
},

BillBuilt · 2022-02-17T16:45:54Z

Edit:
Apparently adding the failing dependencies to SSR noExternal property of vite config, make it work, as @benmccann said before:

I was having this exact issue with @FortAwesome icons and this fixed it

ssr: {
	noExternal: ['@fortawesome/free-brands-svg-icons', '@fortawesome/free-regular-svg-icons', '@fortawesome/free-solid-svg-icons']
},

benmccann · 2022-02-17T17:31:01Z

A better solution for icon libraries is to use this option for performance reasons: https://github.com/sveltejs/vite-plugin-svelte/blob/main/docs/config.md#prebundlesveltelibraries

BillBuilt · 2022-02-17T18:43:47Z

Hi, thanks for the tip! Unfortunately, unless I am doing it wrong, this has no effect. Is this supposed to be uses in addition to the ssr.noExternal setting?

/** @type {import('@sveltejs/kit').Config} */
const config = {
	// Consult https://github.com/sveltejs/svelte-preprocess
	// for more information about preprocessors
	preprocess: preprocess(),

	kit: {
		adapter: adapter(),
		vite: {
			experimental: {
				prebundleSvelteLibraries: true
			},
			resolve: {
				alias: {
					$lib: path.resolve('./src/lib'),
					$comp: path.resolve('./src/components')
				}
			},
		}
	}
}

Produces: SyntaxError: Named export 'faBars' not found. The requested module '@fortawesome/free-solid-svg-icons' is a CommonJS module, which may not support all module.exports as named exports.

I did see this at the link you provided and I deleted the folder but it did not help: When updating the Svelte compiler options in svelte.config.js or vite.config.js, delete the node_modules/.vite folder to trigger pre-bundling in Vite again.

benmccann · 2022-02-17T20:37:57Z

It doesn't go under vite. It goes directly in the root like:

const config = {
	experimental: {
		prebundleSvelteLibraries: true
	}
}

BillBuilt · 2022-02-17T21:53:51Z

hmmm still no change...

/** @type {import('@sveltejs/kit').Config} */
const config = {
	// Consult https://github.com/sveltejs/svelte-preprocess
	// for more information about preprocessors
	preprocess: preprocess(),
	experimental: {
		prebundleSvelteLibraries: true
	},
	kit: {
		adapter: adapter(),
		vite: {
			resolve: {
				alias: {
					$lib: path.resolve('./src/lib'),
					$comp: path.resolve('./src/components')
				}
			},
		}
	}
}

produces at build time:

import { faBars, faHome, faInfo, faTools, faEnvelope } from "@fortawesome/free-solid-svg-icons";
         ^^^^^^
SyntaxError: Named export 'faBars' not found. The requested module '@fortawesome/free-solid-svg-icons' is a CommonJS module, which may not support all module.exports as named exports.

whereas this works fine:

/** @type {import('@sveltejs/kit').Config} */
const config = {
	// Consult https://github.com/sveltejs/svelte-preprocess
	// for more information about preprocessors
	preprocess: preprocess(),

	kit: {
		adapter: adapter(),
		vite: {
			resolve: {
				alias: {
					$lib: path.resolve('./src/lib'),
					$comp: path.resolve('./src/components')
				}
			},
			ssr: {
				noExternal: ['@fortawesome/free-brands-svg-icons', '@fortawesome/free-regular-svg-icons', '@fortawesome/free-solid-svg-icons']
			},
		}
	}
}

I tried swapping out the adapters and noticed that when using adapter-auto it builds but produces the error upon running npm run preview. When using adapter-node it fails at build time.

benmccann · 2022-02-17T22:09:36Z

I'm personally using fort-awesome icons without ssr.noExternal or experimental.prebundleSvelteLibraries in one of my projects by using svelte-awesome:

<script>
	import Icon from 'svelte-awesome';
	import { faTwitter } from '@fortawesome/free-brands-svg-icons';
<script>

<Icon data={faTwitter} scale="1.4"/>

BillBuilt · 2022-02-18T14:44:12Z

I too am using svelte-awesome but for some reason just wants to be finicky!

	import Icon from 'svelte-awesome'
	>>> FAILS: -> import { faBars, faHome, faInfo, faEnvelope, faTools } from '@fortawesome/free-solid-svg-icons'

I'll settle for having to use ssr.noExternal - slightly degraded performance is better than none at all!

benmccann · 2022-02-18T23:04:32Z

Hmm. That seems quite strange. I wonder if you have an old version of Vite or something. You can run rm -rf node_modules package-lock.json && npm install to update. If that still doesn't fix it, please share a repository that reproduces the issue

BillBuilt · 2022-02-22T19:45:32Z

Hey @benmccann,
Sorry for the delayed response - here is a repo you can use to test. I tried deleting and re-installing but with identical results. I'm sure I'm probably just overlooking something.

src/routes/index.svelte has the imports in it. Thanks

https://github.com/BillBuilt/icontest

sveltejs/kit#928

Mnigos · 2022-03-18T13:30:04Z

Just had the same issue and weirdly this solution from layercake issue tracker 👇 worked for me (but with @sanity/client dependency that needs prebundling)

Move vite config to own file vite.config.cjs so that

// vite.config.cjs
const pkg = require('./package.json');

/** @type {import('vite').UserConfig} */
export default {
  ssr: {
    noExternal: Object.keys(pkg.dependencies || {})
  },
};

// svelte.config.cjs
const sveltePreprocess = require('svelte-preprocess');
const node = require('@sveltejs/adapter-node');

/** @type {import('@sveltejs/kit').Config} */
module.exports = {
 preprocess: sveltePreprocess(),
 kit: {
   adapter: node(),
   target: '#svelte',

   // vite: {
   /* moved to vite.config.cjs */
   // }
 }
};

I tried that and still got error ReferenceError: require is not defined in ES module scope, you can use import instead

This allows modern build systems (vite) to properly use the correct module type (ESM). See sveltejs/kit#928 for more details.

* Add package.json exports property This allows modern build systems (vite) to properly use the correct module type (ESM). See sveltejs/kit#928 for more details.

MrEmanuel · 2022-06-05T23:46:04Z

I had similar problems as other people here in the thread.
My use case it that I'm trying to use @googlemaps/js-api-loader.

I got the same error saying it doesn't export a default. So I did a dynamic import in the onMount lifecycle method. Seems to work both in dev and the package compiles a prod build. I also had to update my config.

	onMount(() => {
		// Import loader on mount, because it doesn't have default export, and svelte doesn't like esm modules
		import('@googlemaps/js-api-loader').then((val) => {
			new val.Loader(loaderOptions).load().then(() => {
				map = new google.maps.Map(document.getElementById('map') as HTMLElement, {
					center: startPos,
					zoom: 8,
					styles: mapStyle
				});
			});
		});
	});

/** @type {import('@sveltejs/kit').Config} */
const config = {
	// Consult https://github.com/sveltejs/svelte-preprocess
	// for more information about preprocessors
	preprocess: preprocess(),

	kit: {
		adapter: adapter({
			pages: 'public',
			assets: 'public',
			fallback: null,
			precompress: false
		}),
		prerender: {
			default: false  // 👈
		}
	}
};

ZodiacWind · 2022-06-10T10:01:16Z

hi, I used sveletkit and plotly.js-dist-min in my project. yarn dev could work, but yarn build not. The error message is that:

E:\Projects\leakage-detector\node_modules\rollup\dist\shared\rollup.js:19908
var err = new SyntaxError(message);
^

SyntaxError: Unexpected token (37:121525) in E:/Projects/leakage-detector/node_modules/plotly.js-dist-min/plotly.min.js
at Parser.pp$4.raise (E:\Projects\leakage-detector\node_modules\rollup\dist\shared\rollup.js:19908:13)
at Parser.pp$9.unexpected (E:\Projects\leakage-detector\node_modules\rollup\dist\shared\rollup.js:17202:8)
at Parser.pp$5.parseIdent (E:\Projects\leakage-detector\node_modules\rollup\dist\shared\rollup.js:19839:10)
at Parser.pp$5.parsePropertyName (E:\Projects\leakage-detector\node_modules\rollup\dist\shared\rollup.js:19643:109)
at Parser.pp$5.parseProperty (E:\Projects\leakage-detector\node_modules\rollup\dist\shared\rollup.js:19570:8)
at Parser.pp$5.parseObj (E:\Projects\leakage-detector\node_modules\rollup\dist\shared\rollup.js:19524:21)
at Parser.pp$5.parseExprAtom (E:\Projects\leakage-detector\node_modules\rollup\dist\shared\rollup.js:19259:17)
at Parser.pp$5.parseExprSubscripts (E:\Projects\leakage-detector\node_modules\rollup\dist\shared\rollup.js:19075:19)
at Parser.pp$5.parseMaybeUnary (E:\Projects\leakage-detector\node_modules\rollup\dist\shared\rollup.js:19041:17)
at Parser.pp$5.parseExprOps (E:\Projects\leakage-detector\node_modules\rollup\dist\shared\rollup.js:18968:19) {
pos: 1407827,
loc: {
column: 121525,
file: 'E:/Projects/leakage-detector/node_modules/plotly.js-dist-min/plotly.min.js',
line: 37
},
raisedAt: 1407828,

……

id: 'E:/Projects/leakage-detector/node_modules/plotly.js-dist-min/plotly.min.js',
hook: 'transform',
code: 'PLUGIN_ERROR',
plugin: 'commonjs',

henryennis changed the title ~~issue with using CommonJS modules in svelte/kit build~~ issue with using CommonJS modules in "svelte/kit build" Apr 9, 2021

benmccann added the vite label Apr 9, 2021

benmccann added this to the 1.0 milestone Apr 12, 2021

benmccann closed this as completed Apr 22, 2021

agarzola mentioned this issue Apr 25, 2021

Implement journal functionality agarzola/agarzola-svelte#1

Merged

ecstrema mentioned this issue May 15, 2021

Error when a CJS module is imported from ESM module dependencies vitejs/vite#3024

Closed

Dan6erbond added a commit to Dan6erbond/sk-auth that referenced this issue May 25, 2021

🔧 Create separate Vite config JS according to sveltejs/kit#928

83d23a5

Dan6erbond added a commit to Dan6erbond/sk-auth that referenced this issue May 25, 2021

Revert "🔧 Create separate Vite config JS according to sveltejs/kit#928"

51e73c5

This reverts commit 83d23a5.

SGarno mentioned this issue May 28, 2021

Errors when using RevoGrid with Svelte-kit revolist/svelte-datagrid#2

Closed

raythurnevoid mentioned this issue Jun 18, 2021

SSR Externals False Positive on Windows vitejs/vite#2393

Closed

mathio mentioned this issue Jul 7, 2021

import issues on Netlify, SvelteKit and ViteJS Typeform/embed#288

Closed

AWolf81 mentioned this issue Jul 9, 2021

DB is not connected AWolf81/my_docker_app#1

Open

floratmin mentioned this issue Jul 23, 2021

[xstate/svelte] bundling of @xstate/svelte/lib/fsm with sveltekit & vite is broken statelyai/xstate#2458

Closed

non25 mentioned this issue Sep 25, 2021

Move to ESM to be compatible with Vite/SvelteKit micantoine/svelte-preprocess-cssmodules#34

Closed

Marcosaurios mentioned this issue Oct 12, 2021

Can't deploy to Vercel and Netlify micha-lmxt/svelte-motion#8

Open

josdejong mentioned this issue Nov 17, 2021

vite: TypeError: Cannot set properties of undefined (setting 'j') josdejong/svelte-jsoneditor#31

Closed

keithharvey mentioned this issue Jan 23, 2022

Commonjs modules error leveluptuts/gQuery#19

Closed

colbyhemond mentioned this issue Feb 23, 2022

ArcGIS components causing issues with build codeforUV/ruralnetv2#4

Closed

thecritic mentioned this issue Mar 13, 2022

SvelteKit build failing pablo-abc/felte#112

Closed

evrys added a commit to sprachy/sprachy that referenced this issue Mar 16, 2022

Fix for fontawesome include in vite

daa8114

sveltejs/kit#928

jirihon added a commit to jirihon/euclid.js that referenced this issue Apr 6, 2022

Add package.json exports property

65d9e14

This allows modern build systems (vite) to properly use the correct module type (ESM). See sveltejs/kit#928 for more details.

Marcosaurios mentioned this issue Apr 14, 2022

svelte-motion is completely broken when using with sveltekit... micha-lmxt/svelte-motion#13

Closed

plmercereau mentioned this issue Jun 24, 2022

Cannot build using @nhost/nhost-js with sveltekit nhost/nhost#730

Closed

mariuslundgard mentioned this issue Dec 22, 2022

Cannot read properties of undefined (reading 'deskTool') sanity-io/sanity#4014

Closed

thedevbc mentioned this issue Aug 16, 2023

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/var/task/node_modules/[Some Module]/[Name].esm.js #10468

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

issue with using CommonJS modules in "svelte/kit build" #928

issue with using CommonJS modules in "svelte/kit build" #928

henryennis commented Apr 8, 2021 •

edited

aral commented Apr 8, 2021

henryennis commented Apr 8, 2021

aral commented Apr 9, 2021

benmccann commented Apr 9, 2021 •

edited

aral commented Apr 9, 2021

tolu commented Apr 11, 2021 •

edited

henryennis commented Apr 11, 2021

tolu commented Apr 11, 2021 •

edited

RemyDekor commented Apr 16, 2021 •

edited

benmccann commented Apr 22, 2021

sjmcdowall commented Apr 25, 2021 •

edited

benmccann commented Apr 26, 2021

sjmcdowall commented Apr 26, 2021

ecstrema commented May 15, 2021

praveenkpatare commented Aug 11, 2021

benmccann commented Aug 12, 2021

Marcosaurios commented Oct 12, 2021 •

edited

benmccann commented Oct 12, 2021

Marcosaurios commented Oct 12, 2021

ogrotten commented Dec 20, 2021

BillBuilt commented Feb 17, 2022

benmccann commented Feb 17, 2022

BillBuilt commented Feb 17, 2022

benmccann commented Feb 17, 2022

BillBuilt commented Feb 17, 2022

benmccann commented Feb 17, 2022

BillBuilt commented Feb 18, 2022 •

edited

benmccann commented Feb 18, 2022

BillBuilt commented Feb 22, 2022

Mnigos commented Mar 18, 2022

MrEmanuel commented Jun 5, 2022 •

edited

ZodiacWind commented Jun 10, 2022

issue with using CommonJS modules in "svelte/kit build" #928

issue with using CommonJS modules in "svelte/kit build" #928

Comments

henryennis commented Apr 8, 2021 • edited

aral commented Apr 8, 2021

henryennis commented Apr 8, 2021

aral commented Apr 9, 2021

benmccann commented Apr 9, 2021 • edited

aral commented Apr 9, 2021

tolu commented Apr 11, 2021 • edited

henryennis commented Apr 11, 2021

tolu commented Apr 11, 2021 • edited

RemyDekor commented Apr 16, 2021 • edited

benmccann commented Apr 22, 2021

sjmcdowall commented Apr 25, 2021 • edited

benmccann commented Apr 26, 2021

sjmcdowall commented Apr 26, 2021

ecstrema commented May 15, 2021

praveenkpatare commented Aug 11, 2021

benmccann commented Aug 12, 2021

Marcosaurios commented Oct 12, 2021 • edited

benmccann commented Oct 12, 2021

Marcosaurios commented Oct 12, 2021

ogrotten commented Dec 20, 2021

BillBuilt commented Feb 17, 2022

benmccann commented Feb 17, 2022

BillBuilt commented Feb 17, 2022

benmccann commented Feb 17, 2022

BillBuilt commented Feb 17, 2022

benmccann commented Feb 17, 2022

BillBuilt commented Feb 18, 2022 • edited

benmccann commented Feb 18, 2022

BillBuilt commented Feb 22, 2022

Mnigos commented Mar 18, 2022

MrEmanuel commented Jun 5, 2022 • edited

ZodiacWind commented Jun 10, 2022

henryennis commented Apr 8, 2021 •

edited

benmccann commented Apr 9, 2021 •

edited

tolu commented Apr 11, 2021 •

edited

tolu commented Apr 11, 2021 •

edited

RemyDekor commented Apr 16, 2021 •

edited

sjmcdowall commented Apr 25, 2021 •

edited

Marcosaurios commented Oct 12, 2021 •

edited

BillBuilt commented Feb 18, 2022 •

edited

MrEmanuel commented Jun 5, 2022 •

edited