Error: `The request url * is outside of Vite serving allow list` after git init of submodule inside pnpm monorepo workspace

Question

I have setup a pnpm workspace with a number of projects that I am adding as git submodules.

A previously working Nuxt project suddenly started giving the error The request url * is outside of Vite serving allow list for multiple files, including dependencies installed as pnpm modules inside the workspace node_modules folder.

The only change had been to initialise my project as a git repository.

I was expecting the dev server to keep working, and that changes to git would not have any effect.

The project still builds ok.

Related (unanwsered) questions: stackoverflow.com/questions/74326498/…, stackoverflow.com/questions/74264304/… — a2k42
– a2k42, Commented Dec 23, 2022 at 18:04

Martin · Accepted Answer · 2025-08-28 13:12:47Z

26

The recommended method is to add it to the server.fs.allow list:

import { defineConfig, searchForWorkspaceRoot } from 'vite'
  
export default defineConfig({
  server: {
    fs: {
      allow: [
        // search up for workspace root
        searchForWorkspaceRoot(process.cwd()),
        // your custom rules
        '/path/to/custom/allow',
      ],
    },
  },
})

edited Aug 28 at 13:12

Martin

1081 silver badge12 bronze badges

answered Feb 10, 2023 at 12:34

sancelot

2,07414 silver badges33 bronze badges

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

Comments

kissu · Accepted Answer · 2022-12-23 18:21:41Z

16

Vite uses "auto workspace root detection" to figure out where your project root is.

Within a pnpm workspace your project's node_modules will be installed at the root of the workspace and not within your project folder.

As soon as you initialise a git repository for your project within the workspace then vite seems to auto detect this as your project root and not the workspace (which I'm presuming is initialised as a git repo which you are adding submodules to).

The solution is to specify the pnpm workspace as an allowed directory for the vite server

export default defineNuxtConfig({
    vite: {
        server: {
            fs: {
                allow: ["/home/user/Monorepo"]
            }
        }
    }
})

vite: server-fs-allow

edited Dec 23, 2022 at 18:21

kissu

47.3k16 gold badges94 silver badges197 bronze badges

answered Dec 23, 2022 at 18:02

a2k42

1,4051 gold badge14 silver badges25 bronze badges

8 Comments

Schoenix Over a year ago

Works nice with absolute paths, but couldn't figure out how to make it work with relative paths (better in teams).

Schoenix Over a year ago

I tried this: stackoverflow.com/a/72327029/5935615 but the only thing that worked (but it feels a little bit dirty) is, instead of setting vite.server.fs.allow as you did, setting vite.server.fs.strict to false.

a2k42 Over a year ago

stackoverflow.com/questions/71113423/…

anelec Over a year ago

I've tried this solution with my own user path to the project, but still getting "Failed to load url" and "The request url...is outside of Vite serving allow list" errors. I'm not using pnpm workspace. My Node version is v18.15.0. Nuxt 3.3.3. My Nuxt app also worked fine before initializing as git repository. Now the app is constantly trying to load (browser tab spinning) and does not hot-reload. Is there something I'm missing? Any help appreciated!

a2k42 Over a year ago

@Anelec It's hard to say without knowing what you are using, npm workspace? You might also be able to output the result of searchForWorkspaceRoot to help with debugging and compare this to where your node_modules are in your setup. If that's not enough to resolve the issue then I'd suggest asking your own question and linking it to this one, then you can explain properly what your setup is and how/why this solution isn't working for you. hth

|

Technolo Jesus · Accepted Answer · 2024-07-28 16:09:57Z

5

turn the security off. I have not heard of anything dumber than a secure frontend, its literally a contradiction.

   viteConf.server = {
          ...viteConf.server,
          fs: {
            strict: false // Disable strict file serving restrictions
          }
        };

answered Jul 28, 2024 at 16:09

Technolo Jesus

3624 silver badges10 bronze badges

Comments

liquid_snake · Accepted Answer · 2023-06-06 02:01:03Z

4

If you are using svelte kit, the error might happen when trying to import a file from outside the src folder.

So if you can move said file to that folder, it's an easier fix, otherwise, the answer is @a2k42 's solution.

answered Jun 6, 2023 at 2:01

liquid_snake

1267 bronze badges

Comments

Rmy5 · Accepted Answer · 2023-10-19 12:28:06Z

4

Allow file serving outside of project root with relative path:

server: {
  fs: {
    // Allow serving files from one level up to the project root
    allow: ['..'],
  },
},

answered Oct 19, 2023 at 12:28

Rmy5

5978 silver badges23 bronze badges

Comments

Artur Kwiatkowski · Accepted Answer · 2025-01-10 10:50:44Z

0

I was working with Angular CLI and I created web components with Stencil. I linked this repo with npm link.

I was getting this error because I didn't build the project with components. npm run build fixed this issue for me.

answered Jan 10 at 10:50

Artur Kwiatkowski

113 bronze badges

Collectives™ on Stack Overflow

Error: `The request url * is outside of Vite serving allow list` after git init of submodule inside pnpm monorepo workspace

6 Answers 6

Comments

8 Comments

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

Comments

8 Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related