Error: No loader is configured for ".node" files: node_modules/fsevents/fsevents.node

[xmlking]

Describe the bug

just updated to latest svelte version, I am seeing this error occasionally. it is not happening consistently :(

✘ [ERROR] No loader is configured for ".node" files: node_modules/fsevents/fsevents.node

node_modules/fsevents/fsevents.js:13:23:
  13 │ const Native = require("./fsevents.node");
     ╵                        ~~~~~~~~~~~~~~~~~

6:36:27 PM [vite-plugin-svelte] prebundle libraries done.
package files time avg
svelte-starter-kit 482 2.74s 5.7ms
6:36:27 PM [vite] error while updating dependencies:
Error: Build failed with 1 error:
node_modules/fsevents/fsevents.js:13:23: ERROR: No loader is configured for ".node" files: node_modules/fsevents/fsevents.node
at failureErrorWithLog (/Users/schinth/Developer/Work/SPA/svelte-starter-kit/node_modules/esbuild/lib/main.js:1591:15)
at /Users/schinth/Developer/Work/SPA/svelte-starter-kit/node_modules/esbuild/lib/main.js:1047:28
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
hooks.server.ts, HandleFetch:
errors null

Reproduction

Repo: https://github.com/xmlking/svelte-starter-kit.git

Logs

package                 files    time     avg
svelte-starter-kit        536   0.92s   1.7ms
6:36:23 PM [vite-plugin-svelte] prebundle libraries in progress ...
6:36:27 PM [vite-plugin-svelte] /src/lib/blocks/dashboard/Header1.svelte:20:3 A11y: visible, non-interactive elements with an on:click event must be accompanied by an on:keydown, on:keyup, or on:keypress event.
6:36:27 PM [vite-plugin-svelte] /src/lib/blocks/dashboard/Header1.svelte:30:3 A11y: visible, non-interactive elements with an on:click event must be accompanied by an on:keydown, on:keyup, or on:keypress event.
6:36:27 PM [vite-plugin-svelte] /src/lib/components/PreloadingIndicator.svelte:52:1 Unused CSS selector ":global(html).dark .fade"
✘ [ERROR] No loader is configured for ".node" files: node_modules/fsevents/fsevents.node

    node_modules/fsevents/fsevents.js:13:23:
      13 │ const Native = require("./fsevents.node");
         ╵                        ~~~~~~~~~~~~~~~~~

6:36:27 PM [vite-plugin-svelte] prebundle libraries done.
package                 files    time     avg
svelte-starter-kit        482   2.74s   5.7ms
6:36:27 PM [vite] error while updating dependencies:
Error: Build failed with 1 error:
node_modules/fsevents/fsevents.js:13:23: ERROR: No loader is configured for ".node" files: node_modules/fsevents/fsevents.node
    at failureErrorWithLog (/Users/schinth/Developer/Work/SPA/svelte-starter-kit/node_modules/esbuild/lib/main.js:1591:15)
    at /Users/schinth/Developer/Work/SPA/svelte-starter-kit/node_modules/esbuild/lib/main.js:1047:28
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
hooks.server.ts, HandleFetch:

System Info

npx envinfo --system --binaries --browsers --npmPackages "{svelte,@sveltejs/*,vite}"                                                                                ☸ elrprdusr001_cs-sre_cs-sre-hcc-naas-admin (cs-sre) 
Need to install the following packages:
  envinfo@7.8.1
Ok to proceed? (y) 

  System:
    OS: macOS 12.6.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 1.63 GB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.9.0 - ~/homebrew/bin/node
    npm: 8.19.1 - ~/homebrew/bin/npm
  Browsers:
    Chrome: 108.0.5359.98
    Safari: 16.1
  npmPackages:
    @sveltejs/adapter-auto: 1.0.0-next.90 => 1.0.0-next.90 
    @sveltejs/adapter-node: 1.0.0-next.104 => 1.0.0-next.104 
    @sveltejs/adapter-static: 1.0.0-next.49 => 1.0.0-next.49 
    @sveltejs/kit: 1.0.0-next.587 => 1.0.0-next.587 
    svelte: 3.55.0 => 3.55.0 
    vite: 4.0.1 => 4.0.1

Severity

annoyance

Additional Information

No response

[spabolu]

I have the same issue. I am running on the latest Svelte versions as of Jan 2, 2023.

npx envinfo --system --binaries --browsers --npmPackages "{svelte,@sveltejs/*,vite}"                                                                        
Need to install the following packages:
  envinfo@7.8.1
Ok to proceed? (y) y

  System:
    OS: macOS 13.1
    CPU: (8) arm64 Apple M1
    Memory: 50.94 MB / 8.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 19.2.0 - /opt/homebrew/bin/node
    npm: 8.19.3 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 108.0.5359.124
    Safari: 16.2
  npmPackages:
    @sveltejs/adapter-auto: ^1.0.0 => 1.0.0 
    @sveltejs/kit: ^1.0.1 => 1.0.1 
    @sveltejs/package: ^1.0.1 => 1.0.1 
    svelte: ^3.55.0 => 3.55.0 
    vite: ^4.0.3 => 4.0.3 

Error:

[vorcigernix]

Same here. This is not an issue of the adapter though, it is a compatibility issue on the library side (unfortunately a very common thing).

[Soya-xy]

Encountered the same problem, now what is the solution

[PaHell]

Same problem here.

[tedsteen]

Same here, happened all of a sudden and can't seem to get rid of it. (tried to remove node_modules and .svelte-kit)

EDIT:
seems like VisualCode had auto imported import { loadConfigFromFile } from 'vite' for me and when I removed that the error dissapeared

[oxisto]

Same here, happened all of a sudden and can't seem to get rid of it. (tried to remove node_modules and .svelte-kit)

EDIT: seems like VisualCode had auto imported import { loadConfigFromFile } from 'vite' for me and when I removed that the error dissapeared

I had the exact same issue!

[gtm-nayan]

@xmlking Please update the repo with a proper minimal reproduction as instructed

A link to a repository, or a fork of https://node.new/sveltekit, that reproduces the issue. Reproductions must be short, self-contained and correct and must not contain files or code that aren't relevant to the issue — please do NOT just paste a link to your project.

if you're still running into this otherwise close the issue.

[Rich-Harris]

Closing as no minimal reproduction was provided. Feel free to open a new issue with one.

[RobKohr]

Based on this stack overflow:
https://stackoverflow.com/questions/46929196/how-to-solve-npm-install-throwing-fsevents-warning-on-non-mac-os

I deleted node_modules, and then did a npm install --no-optional and it made the issue go away (just deleting and doing npm install had no effect)

[vorcigernix]

I'd say that this will work only in case that confliction package is one of optional dependencies.

…

On Thu, Mar 9, 2023, 2:09 AM RobKohr ***@***.***> wrote: Based on this stack overflow: https://stackoverflow.com/questions/46929196/how-to-solve-npm-install-throwing-fsevents-warning-on-non-mac-os I deleted node_modules, and then did a npm install --no-optional and it made the issue go away (just deleting and doing npm install had no effect) — Reply to this email directly, view it on GitHub <#8140 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABLZOEWP5MORMXAQF2IZKTW3EUTRANCNFSM6AAAAAAS55MJYY> . You are receiving this because you commented.Message ID: ***@***.***>

[aalakoski]

Not sure if this relevant anymore but I noticed I got the error when I had accidentally imported something that you're not supposed to load / run in the client side. for me it was errors from playwright/test package.. 😅 Removed the unnecessary import and everything is fine.

[jb747]

A number of people have reported that this occurs when vscode auto-imports a package which pulls in fsevents. I think it may be the Svelte extension. In my case, vscode helpfully pulled in 'send' from vite.

[elmir-mammadli]

the only way for me was transpilation of fsevents with nuxt, ts in nuxt.config.ts:

export default {
build: {
transpile: ['fsevents']
}
}

[ccozens]

Same here, happened all of a sudden and can't seem to get rid of it. (tried to remove node_modules and .svelte-kit)

EDIT: seems like VisualCode had auto imported import { loadConfigFromFile } from 'vite' for me and when I removed that the error dissapeared

thank you! I wasted ages on this and found a VS Code auto import import {sortUserPlugins} from 'vite'; for no reason other than to spoil my afternoon.

[Build00rxyz]

I am also having the same issue and none of the solutions are working for me.

[plasmatech8]

For me, it VSCode auto-imported import { build } from 'vite'; which broke my app. You should probably look-out for any imports from vite in your app if you get this error.

[WouS95]

For me removingimport { preview } from 'vite'; fixed the issue. Very strange behaviour.

[Jauki]

ok, it seems to me this problem occurs if you type somehting fast and then not delete it xD happened to me, i wanted to write clg but accidentally wrote slg or something like that and it imported me:

import { splitVendorChunkPlugin } from 'vite';

[YashK-194]

I have the same problem, can anyone tell me in which file did vs code auto import

 import { loadConfigFromFile } from 'vite'

[plasmatech8]

Annoying auto-imports seem to happen all the time. Not sure how to improve that.

[YashK-194]

Found this to turn off auto imports
https://stackoverflow.com/questions/47350589/how-to-disable-automatic-import-statements-in-vscode-october-2017

[carbontwelve]

I have this same issue just from updating Nuxt from 3.7.0 to 3.9.3

[headquarters]

I checked if I had an accidental import from "vite" and didn't see any. I did try disabling all of my optimizeDeps in vite.config.ts, though, and that fixed it. I had made some changes recently to fix "changes detected, restarting server" by including and excluding various dependencies. So, adding "fsevents" to the exclude list for optimizeDeps fixed it:

optimizeDeps: {
  include: [<existing list>],
  exclude: [<existing list>, 'fsevents']
}

[pboling]

Just got a similar error with Svelte 5.0.0-next.133, tried upgrading to Svelte 5.0.0-next.135, also SvelteKit 2.5.8. I've upgraded a lot of packages in the last day and dependabot has been fully broken on pnpm v9 ever since it was released months ago, so I wasn't able to upgrade packages "properly".

Difference is my errors were:

✘ [ERROR] No loader is configured for ".node" files: node_modules/.pnpm/@node-rs+bcrypt-darwin-arm64@1.9.0/node_modules/@node-rs/bcrypt-darwin-arm64/bcrypt.darwin-arm64.node
    node_modules/.pnpm/@node-rs+bcrypt@1.9.0/node_modules/@node-rs/bcrypt/binding.js:165:36:
      165 │             nativeBinding = require('@node-rs/bcrypt-darwin-arm64')

and

✘ [ERROR] No loader is configured for ".node" files: node_modules/.pnpm/@node-rs+argon2-darwin-arm64@1.7.0/node_modules/@node-rs/argon2-darwin-arm64/argon2.darwin-arm64.node
    node_modules/.pnpm/@node-rs+argon2@1.7.0/node_modules/@node-rs/argon2/index.js:173:36:
      173 │             nativeBinding = require('@node-rs/argon2-darwin-arm64')

Being that neither is a direct dependency of the project, I looked to oslo which pulls them in. I had just upgraded to oslo v1.2.0.

Adding this to my vite.config.ts fixed it:

	optimizeDeps: {
		exclude: ['@node-rs/argon2', '@node-rs/bcrypt']
	},

Thanks for all the clues above, everyone!

[danieldiekmeier]

Update: Thanks to #12242, I was able to remove the code again after I updated to SvelteKit 2.5.10. 🥳

---

For me, this started happening in SvelteKit 2.5.8, I'm pretty sure due to the new automatic optimizeDeps.entries from this PR: #12182

As others suggested, I was also able to fix it with:

optimizeDeps: { exclude: ['fsevents'] },

[MahmoodKhalil57]

@pboling Thank you, this worked for me
#8140 (comment)

	optimizeDeps: {
		exclude: ['@node-rs/argon2', '@node-rs/bcrypt']
	},

My original issue
pilcrowonpaper/oslo#75

[j-frost]

I am experiencing this issue too. In my case, I had added

		exclude: ['farmhash']

as indicated by the error message I got.

[danieldiekmeier]

Update: Thanks to #12242, I was able to remove the code again after I updated to SvelteKit 2.5.10. 🥳

[j-frost]

I can confirm what @danieldiekmeier said, I was also able to remove my optimization after an upgrade to 2.5.10.

[pboling]

Same, the "fix" is no longer needed!

[MahmoodKhalil57]

Update: Thanks to #12242, I was able to remove the code again after I updated to SvelteKit 2.5.10. 🥳

same here, can confirm issue is fixed in sveltekit 2.5.10

[chiragpurohit71085]

I was implementing push notification and started having this issue node-pushnotifications

Solution from following link worked.
#8140 (comment)