I have the same problem here. It looks like the output is optimized for browser execution and modules such as "path, fs, etc." do not exist for the browser. This makes sense since it is part of Nodejs itself. It doesn't work in the browser. This is my assumption so far.

Look at the various solutions to understand why I made these assumptions.

https://github.com/vitejs/vite/discussions/6849https://github.com/vitejs/vite/issues/7821#issuecomment- 1142328698

https://github.com/marcofugaro/browserslist-to-esbuildhttps://esbuild.github.io/getting-started/

Given this information, I would prefer a simpler solution to prevent build failures using Vite as a bundler.

Configuration rollupOptions

I think the simplest solution is to define external.https://rollupjs.org/configuration-options/#external

import { resolve } from 'path'; import { defineConfig } from 'vite'; export default defineConfig({ plugins: [], build: { lib: { entry: resolve(__dirname, 'src/index.ts'), name: 'myLib', fileName: 'myLib', }, rollupOptions: { external: [/^node:\w+/], // <-- ignores all 'node:*' }, }, });

Finally found a solution. The problem is caused bypackage.jsonfile conflict.Viteused an incorrectpackage.jsonfile located in the project's parent directory instead of the project's ownpackage.jsonfile. like this - p>

• ~/package.json(wrong file)
• ~/Projects/VueProject/package.json(correct file)

So delete the wrong files and the problem will be solved.

Thanks for the answer to this github questionpackage.json:1:0: Error: Unexpected end of file