Failed to load config from \Project\vuejs-frontend\vite.config.js: VueJS

Question

My Project was running fine yesterday but after revisiting project today I came across this error when trying to run the project.

Here is my vite.config.js file:

import { fileURLToPath, URL } from "node:url";

import { defineConfig } from "vite";
import vue from "@vitejs/plugin-vue";

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [vue()],
  resolve: {
    alias: {
      "@": fileURLToPath(new URL("./src", import.meta.url)),
    },
  },
});

Here is the error I'm getting:

failed to load config from C:\Users\Desktop\Learn\Project\vuejs-frontend\vite.config.js
error when starting dev server:
Error: The service was stopped
    at C:\Users\Desktop\Learn\Project\vuejs-frontend\node_modules\esbuild\lib\main.js:1337:25
    at C:\Users\Desktop\Learn\Project\vuejs-frontend\node_modules\esbuild\lib\main.js:666:9
    at Socket.afterClose (C:\Users\Desktop\Learn\Project\vuejs-frontend\node_modules\esbuild\lib\main.js:644:7)
    at Socket.emit (node:events:539:35)
    at endReadableNT (node:internal/streams/readable:1345:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)

Please share with me any helpful tips you know. Thank you

I saw and used some projects that import fileURLToPath and URL but from url, not node:url. Otherwise looks fine to me — Nicola Spadari
– Nicola Spadari, Commented Jul 18, 2022 at 14:23

Ray Sudana · Accepted Answer · 2022-07-22 07:41:35Z

14

Please check your node version, in my case i update my node version {node: 'v14.17.6'} as showed bellow, and everything goes well.

--- Log --- package: '[email protected]', required: { node: '^14.18.0 || >=16.0.0' }, current: { node: 'v14.17.6', npm: '8.15.0' }

Hope it help

answered Jul 22, 2022 at 7:41

Ray Sudana

1413 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

A.Rahman Al-Khateeb · Accepted Answer · 2024-04-04 15:37:06Z

10

I solved that by:

deleting node_modules/ and package-lock.json.
reinstalling packages with npm install.

npm run dev should work properly now.

answered Apr 4, 2024 at 15:37

A.Rahman Al-Khateeb

1131 silver badge7 bronze badges

2 Comments

Mike Szyndel Over a year ago

What does your answer add to existing 11 answers? Including ones which say to delete node_modules?

A.Rahman Al-Khateeb Over a year ago

deleting only node_modules didn't work for me until I deleted package-lock.json too. No other answer says that.

Smart Manoj · Accepted Answer · 2025-03-16 08:28:31Z

9

I have take a similar error prompt but I am work with react, I just solved this typing the command:

npm update

edited Mar 16 at 8:28

Smart Manoj

6,0736 gold badges45 silver badges66 bronze badges

answered Mar 22, 2023 at 18:48

Hender

4305 silver badges13 bronze badges

Comments

Andrew Killen · Accepted Answer · 2022-12-09 10:00:38Z

4

If you are running a newer verison of node js, I am running 18.x and still want to use Vite, then adapt your code a little bit.

change the code that sets the export default

// vite.config.js
export default defineConfig({
  build: {
    rollupOptions: {
      // https://rollupjs.org/guide/en/#big-list-of-options
    }
  }
})

to be

  const defineConfig = ({
  build: {
    rollupOptions: {
      // https://rollupjs.org/guide/en/#big-list-of-options
    }
  }
});
export default defineConfig;

basically you are setting defineConfig to be a constant and then exporting that. It works fine on any version of node js

answered Dec 9, 2022 at 10:00

Andrew Killen

1,80826 silver badges25 bronze badges

Comments

Pablo · Accepted Answer · 2024-02-14 00:34:44Z

3

I had the same problem and my fix was to remove node_modules folder and then re-run npm install

answered Feb 14, 2024 at 0:34

Pablo

1,26117 silver badges17 bronze badges

Comments

whizboy · Accepted Answer · 2022-10-07 00:50:25Z

The error seems to stem from fact that laravel uses vite 2 while current vite is 3 and yet seems jetstream just installs latest dependencies without considering such. Hence you have to manually try out versions that play well with each other. Currently what worked for me is:

    "@vitejs/plugin-vue": "^2.3.3",
    "laravel-vite-plugin": "^0.2.1",
    "vite": "^2.9.11",
    "vue": "^3.2.31"
    "tailwindcss": "^3.1.0",

it seems the laravel-vite-plugin are laravel-vite-plugin dependencies are the most conflicting.

To make the changes you can edit the package.json and run npm install or npm install the specific packages specifying the version get installation the link from npm for correct format.

This held me down for quite some hours. Thing is not even about node as above answer as myself was on 16.17, though check on that too, upgrading node ended up in up in more problems about openssl because i had postgres installed too which adds the config in path. I did not want to touch that. After fidgeting around creating separate project and installing breeze separately i caught the error.

I got a hint of whats going on from this tweet from Povilas of Laravel daily after hours of scouring the internet.

Question is similar to mine if am not wrong:

check it out

GigaTera · Accepted Answer · 2023-02-26 22:09:51Z

0

I also got the same problem, and it's because your Vite version doesn't match node version.

you need to update your node to the latest, it's very easy.

just download the latest version of node at https://nodejs.org/en/ and your problem will be solved.

answered Feb 26, 2023 at 22:09

GigaTera

1,33713 silver badges17 bronze badges

Comments

fotiecodes · Accepted Answer · 2023-03-22 12:14:53Z

0

I just had the same error while setting up and working with vite, i solved it by importing import { resolve } from 'path' in the my vite.config.js file as seen in the doc here https://vitejs.dev/guide/build.html#library-mode

Hope that helps!

answered Mar 22, 2023 at 12:14

fotiecodes

6267 silver badges12 bronze badges

Comments

codinn.dev · Accepted Answer · 2023-09-04 22:31:41Z

0

Installing the latest node version form Node.js solved the issue for me. Check your version using command -

node -v

My old version was - v14.15.1

New version is - v18.17.1

answered Sep 4, 2023 at 22:31

codinn.dev

2601 silver badge8 bronze badges

Comments

Khaled Ayed · Accepted Answer · 2025-05-12 05:24:45Z

0

I just did rm -rf node_modules and then npm install but the npm install was still displaying esolve error and then i went to win + R and and input cmd and i added this line of command del /f /q

C:\Users\shenc\Documents\tests\node_modules\esbuild-windows-64\esbuild.exe

then i went back to my terminal and did npm install force and boom when i run the npm run dev again it worked without stress.

edited May 12 at 5:24

Khaled Ayed

1,3904 gold badges17 silver badges34 bronze badges

answered May 6 at 21:30

patience okwori

11 bronze badge

1 Comment

julaine May 8 at 7:23

Please format your code-snippets to make it more readable.

Käx · Accepted Answer · 2023-01-06 15:29:56Z

-1

I´m having the same problem but haven´t been able to solve the problem, I thought the problem may have been mine node version but I have 16.17.0.

this is how my vite.config.js file looks:

     import { defineConfig } from "vite";
     import react from "@vitejs/plugin-react";

        export default defineConfig({
           plugins: [react()],
      });

answered Jan 6, 2023 at 15:29

Käx

1

1 Comment

Vojin Purić Over a year ago

This does not really answer the question. If you have a different question, you can ask it by clicking Ask Question. To get notified when this question gets new answers, you can follow this question. Once you have enough reputation, you can also add a bounty to draw more attention to this question. - From Review

Collectives™ on Stack Overflow

Failed to load config from \Project\vuejs-frontend\vite.config.js: VueJS

11 Answers 11

Comments

2 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

11 Answers 11

Comments

2 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related