Nuxt•3mo ago

403 forbidden (parcel etc relative path error)

Windows 11, node v22.13.1 pnpm -v 10.12.1 [GET] "http://127.0.0.1:7459/__nuxt_vite_node__/module/C:/Users/Zubair/node_modules/ufo/dist/index.mjs": 403 Forbidden full error in txt file / at the end (collapse all). pnpm approve-builds and adding in package.json

 "pnpm": {
    "onlyBuiltDependencies": ["@parcel/watcher", "esbuild"]
  },

 "pnpm": {
    "onlyBuiltDependencies": ["@parcel/watcher", "esbuild"]
  },

also not solved this problem. Repo https://github.com/2u841r/travel-log Update: bun install solved this problem. but I mostly use pnpm, which causing problem. deno install also causing problem. (but that's not a problem for me, i mostly not use Deno) and on build-

✔ Generated public .output/public                                                         nitro 12:19:17 AM
ℹ Building Nuxt Nitro server (preset: node-server, compatibility date: 2025-05-15)        nitro 12:19:17 AM
(node:14656) [DEP0155] DeprecationWarning: Use of deprecated trailing slash pattern mapping "./" in the "exports" field module resolution of the package at C:\Users\Zubair\Desktop\M-M\travel-log\node_modules\.pnpm\nuxt@3.17.5_@parcel+watcher_0299fad22698006a1d8f50b7e36a9eda\node_modules\@vue\shared\package.json imported from C:\Users\Zubair\Desktop\M-M\travel-log\node_modules\.pnpm\nuxt@3.17.5_@parcel+watcher_0299fad22698006a1d8f50b7e36a9eda\node_modules\nuxt\dist\core\runtime\nitro\templates\error-dev.js. Mapping specifiers ending in "/" is no longer supported.

✔ Generated public .output/public                                                         nitro 12:19:17 AM
ℹ Building Nuxt Nitro server (preset: node-server, compatibility date: 2025-05-15)        nitro 12:19:17 AM
(node:14656) [DEP0155] DeprecationWarning: Use of deprecated trailing slash pattern mapping "./" in the "exports" field module resolution of the package at C:\Users\Zubair\Desktop\M-M\travel-log\node_modules\.pnpm\nuxt@3.17.5_@parcel+watcher_0299fad22698006a1d8f50b7e36a9eda\node_modules\@vue\shared\package.json imported from C:\Users\Zubair\Desktop\M-M\travel-log\node_modules\.pnpm\nuxt@3.17.5_@parcel+watcher_0299fad22698006a1d8f50b7e36a9eda\node_modules\nuxt\dist\core\runtime\nitro\templates\error-dev.js. Mapping specifiers ending in "/" is no longer supported.

although preview working.

GitHub

GitHub - 2u841r/travel-log

Contribute to 2u841r/travel-log development by creating an account on GitHub.

message.txt

2 Replies

kapa.ai•3mo ago

Hi @Zubair. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- Based on the information in the provided knowledge sources, there is no explicit mention of the exact 403 Forbidden error you are encountering with the Vite node module path (e.g., /__nuxt_vite_node__/module/C:/Users/Zubair/node_modules/ufo/dist/index.mjs) on Windows 11 with Node v22.13.1. However, there are some related issues and context that may help: 1. Windows Path Issues & Node Version: Several issues have been reported with Windows paths and certain Node.js versions in Nuxt 3, especially when using local file paths or when the build/preview process tries to resolve modules using absolute Windows paths. For example, an error involving file:///_entry.js and ERR_INVALID_ARG_VALUE was reported on Windows with Node 18/20, suggesting that path resolution can be problematic in some environments, particularly with Windows-style paths and certain Node versions. The recommendation in that case was to use node .output/server/index.mjs for production rather than nuxt preview and to ensure the environment matches Nuxt's requirements, but there was no direct solution for a 403 error during dev or build modes ERR_INVALID_ARG_VALUE with file:///_entry.js on Windows. 2. Deprecation Warning: The deprecation warning about trailing slash pattern mapping in the "exports" field is a warning and not directly related to the 403 error, but it does indicate that some dependencies (like @vue/shared) may not be fully compatible with the latest Node.js module resolution changes. This could potentially cause issues in some setups, but the knowledge sources do not provide a direct fix for this warning. 3. General Advice: When encountering 403 errors for module files in development, it often points to a misconfiguration in the dev server, file permissions, or an incompatibility between the toolchain (Vite, Nuxt, Node.js) and the operating system. None of the knowledge sources provide a step-by-step solution for this specific error, but similar issues have sometimes been resolved by: - Ensuring all dependencies are up to date and compatible with your Node.js version. - Deleting node_modules and lock files, then reinstalling dependencies. - Trying a different Node.js version (e.g., downgrading to Node 20 or 18 if using Node 22). - Checking for custom configuration in nuxt.config.ts that might affect Vite or Nitro server behavior. Summary:
I'm sorry, but the knowledge sources do not contain enough information to provide a definitive solution for the 403 Forbidden error you are experiencing with the Vite node module path on Windows 11 and Node v22.13.1. The issue may be related to Windows path handling or Node.js version compatibility, but no direct fix is documented in the sources provided. If possible, try using Node 20 or 18, ensure your dependencies are up to date, and check for any custom configuration that might affect module resolution. If the problem persists, consider opening a new issue on the Nuxt GitHub repository with detailed reproduction steps. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•3mo ago

<@580667111253213185> Kapa.ai is still learning and improving, please let me know how I did by reacting below.

Gaming

Programming

403 forbidden (parcel etc relative path error)

Did you find this page helpful?