[Nitro/Unenv] cloudflare_pages build error: Could not resolve import string_decoder #1821

andrevandal · 2023-10-11T17:34:44Z

Environment

node: 18.16.1
nuxt: 3.7.4
drizzle-kit: 0.19.13
@nuxtjs/tailwindcss: 6.8.0
@planetscale/database: 1.11.0
drizzle-orm: 0.28.6
pnpm: 8.9.0

Reproduction

Clone the repo: https://github.com/andrevandal/ondevamos-web/tree/start-backend
Build.

I tried to build it through pnpm and npm, but both got errors.

Describe the bug

When building the nuxt project, we got the error:

ℹ Building Nitro Server (preset: cloudflare_pages)                           nitro 2:18:00 PM
(node-resolve plugin) Could not resolve import "unenv/runtime/node/string_decoder/index/" in /Users/andre.vandal/projects/github.com/andrevandal/ondevamos-web/node_modules/readable-stream/lib/_stream_readable.js using exports defined in /Users/andre.vandal/projects/github.com/andrevandal/ondevamos-web/node_modules/unenv/package.json.

[nitro 2:18:03 PM]  ERROR  Error: Cannot resolve "unenv/runtime/node/string_decoder/index/" from "/Users/andre.vandal/projects/github.com/andrevandal/ondevamos-web/node_modules/readable-stream/lib/_stream_readable.js" and externals are not allowed!


undefined


[2:18:03 PM]  ERROR  Cannot resolve "unenv/runtime/node/string_decoder/index/" from "/Users/andre.vandal/projects/github.com/andrevandal/ondevamos-web/node_modules/readable-stream/lib/_stream_readable.js" and externals are not allowed!

  at Object.resolveId (node_modules/nuxt/node_modules/nitropack/dist/shared/nitro.0093b44c.mjs:1879:17)
  at async PluginDriver.hookFirstAndGetPlugin (node_modules/rollup/dist/es/shared/node-entry.js:25444:28)
  at async resolveId (node_modules/rollup/dist/es/shared/node-entry.js:24117:26)
  at async ModuleLoader.resolveId (node_modules/rollup/dist/es/shared/node-entry.js:24531:15)
  at async PluginDriver.hookFirstAndGetPlugin (node_modules/rollup/dist/es/shared/node-entry.js:25444:28)
  at async resolveId (node_modules/rollup/dist/es/shared/node-entry.js:24117:26)
  at async ModuleLoader.resolveId (node_modules/rollup/dist/es/shared/node-entry.js:24531:15)
  at async node_modules/@rollup/plugin-commonjs/dist/es/index.js:781:16
  at async Promise.all (index 10)
  at async node_modules/@rollup/plugin-commonjs/dist/es/index.js:773:32

Additional context

Related issues:

Logs

No response

The text was updated successfully, but these errors were encountered:

DHartenfels · 2023-10-12T19:42:43Z

I've got the same error with "vercel-edge" Preset:

ℹ Building Nitro Server (preset: vercel-edge)                                    nitro 21:32:11
(node-resolve plugin) Could not resolve import "unenv/runtime/node/string_decoder/index/" in D:\BisschenProggen\shopifyInspector\node_modules\lambdafs\node_modules\tar-stream\node_modules\readable-stream\lib\_stream_readable.js using exports defined in D:\BisschenProggen\shopifyInspector\node_modules\unenv\package.json.

[nitro 21:32:13]  ERROR  Error: Cannot resolve "unenv/runtime/node/string_decoder/index/" from "D:\\BisschenProggen\\shopifyInspector\\node_modules\\lambdafs\\node_modules\\tar-stream\\node_modules\\readable-stream\\lib\\_stream_readable.js" and externals are not allowed!


undefined


[21:32:13]  ERROR  Cannot resolve "unenv/runtime/node/string_decoder/index/" from "D:\\BisschenProggen\\shopifyInspector\\node_modules\\lambdafs\\node_modules\\tar-stream\\node_modules\\readable-stream\\lib\\_stream_readable.js" and externals are not allowed!

  at Object.resolveId (/D:/BisschenProggen/shopifyInspector/node_modules/nitropack/dist/shared/nitro.0093b44c.mjs:1879:17)
  at async PluginDriver.hookFirstAndGetPlugin (/D:/BisschenProggen/shopifyInspector/node_modules/rollup/dist/es/shared/node-entry.js:25444:28)
  at async resolveId (/D:/BisschenProggen/shopifyInspector/node_modules/rollup/dist/es/shared/node-entry.js:24117:26)
  at async ModuleLoader.resolveId (/D:/BisschenProggen/shopifyInspector/node_modules/rollup/dist/es/shared/node-entry.js:24531:15)
  at async PluginDriver.hookFirstAndGetPlugin (/D:/BisschenProggen/shopifyInspector/node_modules/rollup/dist/es/shared/node-entry.js:25444:28)
  at async resolveId (/D:/BisschenProggen/shopifyInspector/node_modules/rollup/dist/es/shared/node-entry.js:24117:26)
  at async ModuleLoader.resolveId (/D:/BisschenProggen/shopifyInspector/node_modules/rollup/dist/es/shared/node-entry.js:24531:15)
  at async /D:/BisschenProggen/shopifyInspector/node_modules/@rollup/plugin-commonjs/dist/es/index.js:781:16
  at async Promise.all (index 10)
  at async /D:/BisschenProggen/shopifyInspector/node_modules/@rollup/plugin-commonjs/dist/es/index.js:773:32



[21:32:13]  ERROR  Cannot resolve "unenv/runtime/node/string_decoder/index/" from "D:\\BisschenProggen\\shopifyInspector\\node_modules\\lambdafs\\node_modules\\tar-stream\\node_modules\\readable-stream\\lib\\_stream_readable.js" and externals are not allowed!

This is my package.json file:

{
  "name": "nuxt-app",
  "private": true,
  "type": "module",
  "scripts": {
    "build": "nuxt build",
    "dev": "nuxt dev",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "postinstall": "nuxt prepare"
  },
  "devDependencies": {
    "@nuxt/devtools": "latest",
    "@nuxtjs/tailwindcss": "^6.8.0",
    "nuxt": "^3.7.4",
    "unenv": "^1.7.4",
    "vue": "^3.3.4",
    "vue-router": "^4.2.5"
  },
  "dependencies": {
    "chrome-aws-lambda": "^10.1.0",
    "puppeteer": "^10.1.0",
    "puppeteer-core": "^10.4.0"
  }
}

Building on

Building Nitro Server (preset: node-server)

is fine without any problems

Gruce · 2023-10-20T23:39:39Z

Same but a different module:

[error] [nitro] Error: Cannot resolve "bufferutil" from "/opt/buildhome/repo/node_modules/.pnpm/[email protected]/node_modules/ws/lib/buffer-util.js" and externals are not allowed!

vptill · 2023-10-31T14:29:50Z

Having the same issue

[error] Cannot resolve "unenv/runtime/node/string_decoder/index/" from "/opt/buildhome/repo/node_modules/imap/node_modules/readable-stream/lib/_stream_readable.js" and externals are not allowed!

ManasMadrecha · 2023-11-03T12:33:37Z

Any solution to this? I am currently on firebase preset (with no error) and want to try cloudflare. Changing the preset to cloudflare-pages gives this error.

aw-0 · 2023-12-16T00:52:10Z

Currently trying to build via the deployment guide for cloudflare and getting this exact same error. Any updates on this?

megatheikal · 2024-01-10T01:46:21Z

Same but a different module:

[error] [nitro] Error: Cannot resolve "bufferutil" from "/opt/buildhome/repo/node_modules/.pnpm/[email protected]/node_modules/ws/lib/buffer-util.js" and externals are not allowed!

try yarn add bufferutil utf-8-validate. it worked for me

Gruce · 2024-01-10T11:38:12Z

Same but a different module:
[error] [nitro] Error: Cannot resolve "bufferutil" from "/opt/buildhome/repo/node_modules/.pnpm/[email protected]/node_modules/ws/lib/buffer-util.js" and externals are not allowed!
try yarn add bufferutil utf-8-validate. it worked for me

This workaround confirmed.

But it may cause another bug on cloudflare:

Thank you.

zakarialounes · 2024-01-11T02:41:05Z

In my nuxt.config.ts file I have this, if it helps

    rollupConfig: {
      external: ["bufferutil", "utf-8-validate"],
      output: {
        generatedCode: {
          symbols: true,
        },
      },
    },

HassanKadhim · 2024-01-12T18:30:34Z

In my nuxt.config.ts file I have this, if it helps

    rollupConfig: {
      external: ["bufferutil", "utf-8-validate"],
      output: {
        generatedCode: {
          symbols: true,
        },
      },
    },

Same problem, nothing changed.

andrevandal · 2024-01-16T15:17:45Z

the problem is that unenv ins't converting JavaScript code to Cloudflare compatible code.

adding modules to external (#1821 (comment)) just says to rollup this module will be available in runtime, which isn't (#1821 (comment)).

this is the map table of how unenv convert some modules:
https://github.com/unjs/unenv?tab=readme-ov-file#built-in-nodejs-modules

elliotjarnit · 2024-01-30T15:48:56Z

Was a solution ever found to @andrevandal's problem? It seems like him and many others are experiencing the same issue with no luck.

pi0 · 2024-02-02T09:45:27Z

Hi. We are aware and this issue is under the track.

The issue is that you are using a library that is designed for Node.js and when trying to deploy to Cloudflare pages, Nitro (while trying to fix this with unenv) is not covering some subpath compatibility.

I should spend more time investigating what exact library is incompatible and a minimal (nitro only with only problematic dependency) could help to speed this up.

milindanath · 2024-02-04T16:30:10Z

I got the exact same issue when importing firebase-admin inside a nitro plugin. But I figured out that it was the import that was incorrect. A minimal reproduction can be found at https://stackblitz.com/edit/github-znntty

The incorrect version was

import admin from 'firebase-admin';

export default defineNitroPlugin((nitro) => {
  const test = admin.initializeApp;
});

The errors disappeared after correcting the code to the following.

import { initializeApp } from 'firebase-admin/app';

export default defineNitroPlugin((nitro) => {
  const test = initializeApp;
});

kylebuxton · 2024-02-04T19:32:36Z

I got the exact same issue when importing firebase-admin inside a nitro plugin. But I figured out that it was the import that was incorrect. A minimal reproduction can be found at https://stackblitz.com/edit/github-znntty

The incorrect version was
import admin from 'firebase-admin';

export default defineNitroPlugin((nitro) => {
  const test = admin.initializeApp;
});
The errors disappeared after correcting the code to the following.
import { initializeApp } from 'firebase-admin/app';

export default defineNitroPlugin((nitro) => {
  const test = initializeApp;
});

I made this change but it didn't work on my end, I'm still getting the same error "Cannot resolve "unenv/runtime/node/string_decoder/index/""

elliotjarnit · 2024-02-20T21:36:20Z

after some research the problem seems to be with
import {getFirestore} from "firebase-admin/firestore";
as when I remove this import, building works perfectly.

I don't know why this could be but I will keep looking.

AmirMechouk · 2024-03-12T18:04:58Z

Can add the following library also to the issue list
[nitro] Error: Cannot resolve "aws-sdk" from "/opt/atlassian/pipelines/agent/build/node_modules/@opensearch-project/opensearch/lib/aws/AwsSigv4Signer.js" and externals are not allowed!

Mgoeloe · 2024-04-12T00:40:35Z

Same with KnexJS

[error] [nitro] Error: Cannot resolve "pg" from "/opt/buildhome/repo/node_modules/knex/lib/dialects/redshift/index.js" and externals are not allowed!

mrbubbaz · 2024-05-03T10:33:41Z

Same with String_decoder (?)

[error] Cannot resolve "unenv/runtime/node/string_decoder/index/" from "/opt/buildhome/repo/node_modules/readable-stream/lib/_stream_readable.js" and externals are not allowed!

chuckntaylor · 2024-05-03T13:11:19Z

Any chance you have set an env variable like NODE_ENV=production?

If you did, then it is possible that the development dependencies are not being installed by Cloudflare before the build phase. For my purposes, I did want to set NODE_ENV for my development and production builds and so I had to make sure that development dependencies were installed.

npm install --include=dev

If you are trying to run different commands for different branches, I would recommend the following:

Create separate build scripts in your package.json. Could be something like:

"scripts": {
    "build": "vite build",
    "build:dev": "vite build --mode development",
  }

Create a new file at your project root build.sh - Make sure to update if CF_PAGES_BRANCH statements with the name of your git branches. I am using branches prod and dev in my example.

# !/bin/bash

if [ "$CF_PAGES_BRANCH" == "prod" ]; then
  # Run the "production" script in `package.json` on the "prod" branch
  # "prod" should be replaced with the name of your Production branch

  echo "In Production - make sure dev dependencies are installed"
  npm install --include=dev
  echo "Building for Production"
  npm run build

elif [ "$CF_PAGES_BRANCH" == "dev" ]; then
  # Run the "dev" script in `package.json` on the "dev" branch
  # "dev" should be replaced with the name of your specific branch

  echo "Building for Development"
  npm run build:dev

else
  # Else run the dev script
  echo "Unrecognized Branch: $CF_PAGES_BRANCH"
  npm run build:dev
fi

Lastly, in your Cloudflare dashboard for the project, make sure you specify the build command to be bash build.sh

This will make sure that your branch prod in my example is running npm install --include=dev before the build, and is installing all the packages.

CodyBontecou · 2024-06-23T01:03:07Z

Hi. We are aware and this issue is under the track.

The issue is that you are using a library that is designed for Node.js and when trying to deploy to Cloudflare pages, Nitro (while trying to fix this with unenv) is not covering some subpath compatibility.

I should spend more time investigating what exact library is incompatible and a minimal (nitro only with only problematic dependency) could help to speed this up.

This ended up being the issue. My specific dependency was node-telegram-bot-api. After removing it, the build was successful.

Something worth noting - this error was happening even during my local build, not specific to cloudflare.

provok-me · 2024-06-30T16:06:24Z

Same with Netlify (netlify_edge) and Sharp:

[error] [nitro] Error: Cannot resolve "@img/sharp-wasm32/versions" from "/opt/build/repo/node_modules/.pnpm/[email protected]/node_modules/sharp/lib/utility.js" and externals are not allowed!

zou-yu · 2024-07-06T02:23:02Z

Any updates? I'am facing same problem with argon2:


[error] [nitro] Error: Cannot resolve "./argon2.win32-x64-msvc.node" from "/opt/buildhome/repo/node_modules/.pnpm/@[email protected]/node_modules/@node-rs/argon2/index.js" and externals are not allowed!
--

Pachara · 2024-07-17T12:27:37Z

No body sloved this issue ?
I got exactly same error

[info] [nitro] Building Nuxt Nitro server (preset: `cloudflare-pages`)

19:06:13.652 | [plugin node-resolve] Could not resolve import "unenv/runtime/node/string_decoder/index/" in /opt/buildhome/repo/node_modules/readable-stream/lib/_stream_readable.js using exports defined in /opt/buildhome/repo/node_modules/unenv/package.json.

Mgoeloe · 2024-07-17T13:00:17Z

No body sloved this issue ?
I got exactly same error

[info] [nitro] Building Nuxt Nitro server (preset: cloudflare-pages)

19:06:13.652 | [plugin node-resolve] Could not resolve import "unenv/runtime/node/string_decoder/index/" in /opt/buildhome/repo/node_modules/readable-stream/lib/_stream_readable.js using exports defined in /opt/buildhome/repo/node_modules/unenv/package.json.

Using polyfills might work.

Pachara · 2024-07-17T15:38:05Z

No body sloved this issue ?
I got exactly same error

[info] [nitro] Building Nuxt Nitro server (preset: cloudflare-pages)

19:06:13.652 | [plugin node-resolve] Could not resolve import "unenv/runtime/node/string_decoder/index/" in /opt/buildhome/repo/node_modules/readable-stream/lib/_stream_readable.js using exports defined in /opt/buildhome/repo/node_modules/unenv/package.json.

Using polyfills might work.

I try, It not working.
No mater what we try to by pass, it not working

ryoid · 2024-07-24T17:05:51Z

Hi. We are aware and this issue is under the track.

The issue is that you are using a library that is designed for Node.js and when trying to deploy to Cloudflare pages, Nitro (while trying to fix this with unenv) is not covering some subpath compatibility.

I should spend more time investigating what exact library is incompatible and a minimal (nitro only with only problematic dependency) could help to speed this up.

Encountered similar issue, was not sure if I should comment here so I made a new issue with minimal repro. #2631

Dmytro-Tihunov · 2024-08-05T08:43:18Z

faced with same, is there any updates?

clopezpro · 2024-08-14T19:19:47Z

Same with Netlify (netlify_edge) and Sharp:

[error] [nitro] Error: Cannot resolve "@img/sharp-wasm32/versions" from "/opt/build/repo/node_modules/.pnpm/[email protected]/node_modules/sharp/lib/utility.js" and externals are not allowed!

Maybe it's because I use NuxtImg

<body>
<!--StartFragment-->
14:10:46.355 | [info] .nuxt/dist/server/server.mjs                                          395.63 kB │ map: 880.46 kB
-- | --
14:10:46.356 | [info] ✓ built in 13.29s
14:10:46.358 | [success] Server built in 13306ms
14:10:46.472 | [success] [nitro] Generated public dist
14:10:46.512 | [info] [nitro] Building Nuxt Nitro server (preset: `cloudflare-pages`)
14:11:03.363 | [error] [nitro] Error: Cannot resolve "@img/sharp-wasm32/versions" from "/opt/buildhome/repo/node_modules/sharp/lib/utility.js" and externals are not allowed!
14:11:03.363 |  
14:11:03.363 |  
14:11:03.363 | undefined
14:11:03.367 | [error] Cannot resolve "@img/sharp-wasm32/versions" from "/opt/buildhome/repo/node_modules/sharp/lib/utility.js" and externals are not allowed!
14:11:03.367 | at Object.resolveId (node_modules/nitropack/dist/nitro.mjs:1970:17)
14:11:03.368 | at async PluginDriver.hookFirstAndGetPlugin (node_modules/rollup/dist/es/shared/node-entry.js:19674:28)
14:11:03.368 | at async resolveId (node_modules/rollup/dist/es/shared/node-entry.js:18355:26)
14:11:03.368 | at async ModuleLoader.resolveId (node_modules/rollup/dist/es/shared/node-entry.js:18758:15)
14:11:03.368 | at async node_modules/@rollup/plugin-commonjs/dist/es/index.js:785:16
14:11:03.368 | at async Promise.all (index 5)
14:11:03.368 | at async node_modules/@rollup/plugin-commonjs/dist/es/index.js:777:32
14:11:03.369 | at async rewriteRequireExpressionsAndGetImportBlock (node_modules/@rollup/plugin-commonjs/dist/es/index.js:1354:28)
14:11:03.369 | at async transformCommonjs (node_modules/@rollup/plugin-commonjs/dist/es/index.js:1933:23)
14:11:03.370 | at async transform (node_modules/rollup/dist/es/shared/node-entry.js:18676:16)
14:11:03.371 |  
14:11:03.371 | [error] Cannot resolve "@img/sharp-wasm32/versions" from "/opt/buildhome/repo/node_modules/sharp/lib/utility.js" and externals are not allowed!
14:11:03.599 | Failed: Error while executing user command. Exited with error code: 1
14:11:03.610 | Failed: build command exited with code: 1
14:11:05.352 | Failed: error occurred while running build command

<!--EndFragment-->
</body>
</html>
```

alexis-fresard · 2024-08-16T11:36:40Z

Solution found !

Hello everyone, I found a solution to this problem that worked for me.

In my project folder. I went to the file nuxt.config.ts and I added the following lines

export default {
  alias: {
    'string_decoder': 'string_decoder/',
  },
}

Then I built the project and now it works perfectly for me.

timpulver · 2024-08-21T13:21:50Z

Same issue with vue3-moveable on NuxtHub (cloudflare-pages preset):

[info] [nitro] Building Nuxt Nitro server (preset: cloudflare-pages)
[error] [nitro] Error: Cannot resolve "vue3-moveable" from "/opt/buildhome/repo/.nuxt/dist/server/_nuxt/id.client-BV76-_Rs.js" and externals are not allowed!

This happens with default exports, as well as named exports.

Are there any workarounds or ways how to find out which sub-dependencies are causing the problem?

brendonmatos · 2024-08-24T20:25:28Z

alias: {
'string_decoder': 'string_decoder/',
},

Solved my issue! Thanks

paulvonber · 2024-08-27T17:44:54Z

all the solutions provided didn't help. Is there anything else not posted here yet that could help?

sugoidesune · 2024-09-19T01:20:12Z

I can deploy nuxt with

ssr: false

but with true i get that error.
This fixed it. Throws an error during render but it works.

export default {
  alias: {
    'string_decoder': 'string_decoder/',
  },
}

▲ [WARNING] Non-relative path "string_decoder/" is not allowed when "baseUrl" is not set (did you forget a leading "./"?) [tsconfig.json]

In the end the worker exceeded 1MiB so i couldn't test yet.

Aybee5 · 2024-10-08T18:11:01Z

Solution found !

Hello everyone, I found a solution to this problem that worked for me.

In my project folder. I went to the file nuxt.config.ts and I added the following lines
export default {
  alias: {
    'string_decoder': 'string_decoder/',
  },
}
Then I built the project and now it works perfectly for me.

This works for building, but now my server route is returning 500, I am using the node-telegram-bot-api package

DavidFrings · 2024-11-05T10:36:57Z

I have the same problem...

Here is a shortet version of my logs:

Detected the following tools from environment: nodejs@20.12.2, pnpm@9.12.2
dependencies:
	+ hammerjs 2.0.8
	+ nuxt 3.13.2
	+ prettier 3.3.3
	+ vue 3.5.11
	+ vue-router 4.4.5
	
devDependencies:
	+ @emotion/css 11.13.4
	+ @nuxtjs/i18n 9.0.0-rc.2
	+ @nuxtjs/sitemap 6.1.2
	+ @vite-pwa/nuxt 0.10.5
	+ nuxt-security 2.0.0

Executing user command: pnpm install && pnpm run format && pnpm run build --if-present

> nuxt build "--if-present"
[log] Nuxt 3.13.2 with Nitro 2.9.7
[success] Client built in 2496ms
[info] Building server...
[info] �[vite v5.4.8] building SSR bundle for production...�
[plugin] [unplugin-vue-i18n:directive] Sourcemap is likely to be incorrect: a plugin (unplugin-vue-i18n:directive) was used to transform files, but didn't generate a sourcemap for the transformation. Consult the plugin documentation for help
[success] Server built in 1705ms
[success] [nitro] Generated public dist

PWA v0.20.5
mode      generateSW
precache  3 entries (0.41 KiB)
files generated
 dist/sw.js
 dist/workbox-cbf83eee.js

[info] [nitro] Building Nuxt Nitro server (preset: `cloudflare_pages`)
[error] [nitro] RollupError: .nuxt/dist/server/_nuxt/prompt-BGYTzdFy.js (1:9): "stdin" is not exported by "node_modules/.pnpm/[email protected]/node_modules/unenv/runtime/node/process/index.mjs", imported by ".nuxt/dist/server/_nuxt/prompt-BGYTzdFy.js".


1: import { stdin, stdout } from "node:process";
	            ^
2: import f from "node:readline";
3: import { WriteStream } from "node:tty";

[error] .nuxt/dist/server/_nuxt/prompt-BGYTzdFy.js (1:9): "stdin" is not exported by "node_modules/.pnpm/[email protected]/node_modules/unenv/runtime/node/process/index.mjs", imported by ".nuxt/dist/server/_nuxt/prompt-BGYTzdFy.js".
	  at getRollupError (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/parseAst.js:395:41)
	  at error (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/parseAst.js:391:42)
	  at Module.error (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:15535:16)
	  at Module.traceVariable (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:15984:29)
	  at ModuleScope.findVariable (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:13770:39)
	  at ChildScope.findVariable (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:5252:38)
	  at ClassBodyScope.findVariable (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:5252:38)
	  at ChildScope.findVariable (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:5252:38)
	  at ChildScope.findVariable (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:5252:38)
	  at FunctionScope.findVariable (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:5252:38)
	  at Identifier.bind (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:5035:40)
	  at AssignmentPattern.bind (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:2855:23)
	  at Property.bind (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:2855:23)
	  at ObjectPattern.bind (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:2851:28)
	  at FunctionExpression.bind (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:2851:28)
	  at MethodDefinition.bind (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:2855:23)
	  at ClassBody.bind (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:2851:28)
	  at ClassDeclaration.bind (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:2855:23)
	  at Program.bind (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:2851:28)
	  at Module.bindReferences (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:15514:18)
	  at Graph.sortModules (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:21019:20)
	  at Graph.build (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:20922:14)
	  at async node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:21607:13
	  at async catchUnfinishedHookActions (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:21076:16)
	  at async rollupInternal (node_modules/.pnpm/rollup@4.24.0/node_modules/rollup/dist/es/shared/node-entry.js:21602:5)
	  at async _build (node_modules/.pnpm/nitropack@2.9.7_magicast@0.3.5/node_modules/nitropack/dist/nitro.mjs:2633:20)
	  at async node_modules/.pnpm/nuxt@3.13.2_@parcel+watcher@2.4.1_@types+node@22.7.4_eslint@9.13.0_jiti@2.3.1__ioredis@5.4.1__5dzmqmjnledb6iljrfoadnkny4/node_modules/nuxt/dist/index.mjs:3630:5
	  at async build (node_modules/.pnpm/nuxt@3.13.2_@parcel+watcher@2.4.1_@types+node@22.7.4_eslint@9.13.0_jiti@2.3.1__ioredis@5.4.1__5dzmqmjnledb6iljrfoadnkny4/node_modules/nuxt/dist/index.mjs:5778:3)
	  at async Object.run (node_modules/.pnpm/nuxi@3.14.0/node_modules/nuxi/dist/chunks/build.mjs:101:5)
	  at async runCommand$1 (node_modules/.pnpm/nuxi@3.14.0/node_modules/nuxi/dist/shared/nuxi.3e201632.mjs:1648:16)
	  at async runCommand$1 (node_modules/.pnpm/nuxi@3.14.0/node_modules/nuxi/dist/shared/nuxi.3e201632.mjs:1639:11)
	  at async runMain$1 (node_modules/.pnpm/nuxi@3.14.0/node_modules/nuxi/dist/shared/nuxi.3e201632.mjs:1777:7) 

[error] .nuxt/dist/server/_nuxt/prompt-BGYTzdFy.js (1:9): "stdin" is not exported by "node_modules/.pnpm/[email protected]/node_modules/unenv/runtime/node/process/index.mjs", imported by ".nuxt/dist/server/_nuxt/prompt-BGYTzdFy.js".
Command failed with exit code 1.

Is it because of the ssr?

Can someone help me?

DavidFrings · 2024-11-12T05:45:49Z

nuxt-modules/sitemap#380 (comment)

worked for me...

andrevandal added the pending triage label Oct 11, 2023

andrevandal mentioned this issue Oct 11, 2023

Buid giving the error in cloudflare-pages preset unjs/unenv#129

Closed

Hebilicious added the unenv label Oct 23, 2023

bllchmbrs mentioned this issue Dec 31, 2023

Error: Cannot resolve "cloudflare:sockets" from "...\node_modules\.pnpm\[email protected]\node_modules\postgres\cf\polyfills.js" and externals are not allowed! porsager/postgres#727

Closed

manniL added bug Something isn't working and removed pending triage labels Jan 3, 2024

This comment was marked as duplicate.

Sign in to view

pi0 mentioned this issue Feb 2, 2024

cloudflare_pages build error nuxt/nuxt#25578

Closed

lovell mentioned this issue May 23, 2024

Nuxt build failed on Cloudflare Pages. Cannot resolve "@img/sharp-wasm32/versions". lovell/sharp#4113

Closed

3 tasks

anbraten mentioned this issue Jul 4, 2024

Cannot resolve "unenv/runtime/node/string_decoder/index/" unjs/unenv#281

Closed

ryoid mentioned this issue Jul 24, 2024

Cloudflare Pages build fails. Cannot resolve "unenv/runtime/node/process/index/" #2631

Open

iBobik mentioned this issue Nov 5, 2024

Add support for non-Node worker environments googleapis/google-cloud-node#5786

Open

[Nitro/Unenv] cloudflare_pages build error: Could not resolve import string_decoder #1821

[Nitro/Unenv] cloudflare_pages build error: Could not resolve import string_decoder #1821

Comments

andrevandal commented Oct 11, 2023

Environment

Reproduction

Describe the bug

Additional context

Logs

DHartenfels commented Oct 12, 2023

Gruce commented Oct 20, 2023 • edited Loading

vptill commented Oct 31, 2023

ManasMadrecha commented Nov 3, 2023

aw-0 commented Dec 16, 2023 • edited Loading

megatheikal commented Jan 10, 2024

Gruce commented Jan 10, 2024 • edited Loading

zakarialounes commented Jan 11, 2024 • edited Loading

HassanKadhim commented Jan 12, 2024

andrevandal commented Jan 16, 2024

elliotjarnit commented Jan 30, 2024

This comment was marked as duplicate.

This comment was marked as duplicate.

pi0 commented Feb 2, 2024

milindanath commented Feb 4, 2024

kylebuxton commented Feb 4, 2024

elliotjarnit commented Feb 20, 2024

AmirMechouk commented Mar 12, 2024

Mgoeloe commented Apr 12, 2024

mrbubbaz commented May 3, 2024

chuckntaylor commented May 3, 2024

CodyBontecou commented Jun 23, 2024

provok-me commented Jun 30, 2024 • edited Loading

zou-yu commented Jul 6, 2024

Pachara commented Jul 17, 2024

[info] [nitro] Building Nuxt Nitro server (preset: cloudflare-pages)

Mgoeloe commented Jul 17, 2024

[info] [nitro] Building Nuxt Nitro server (preset: cloudflare-pages)

Pachara commented Jul 17, 2024

[info] [nitro] Building Nuxt Nitro server (preset: cloudflare-pages)

ryoid commented Jul 24, 2024 • edited Loading

Dmytro-Tihunov commented Aug 5, 2024

clopezpro commented Aug 14, 2024

alexis-fresard commented Aug 16, 2024

Solution found !

timpulver commented Aug 21, 2024 • edited Loading

brendonmatos commented Aug 24, 2024

paulvonber commented Aug 27, 2024

sugoidesune commented Sep 19, 2024 • edited Loading

Aybee5 commented Oct 8, 2024

Solution found !

DavidFrings commented Nov 5, 2024

DavidFrings commented Nov 12, 2024

Gruce commented Oct 20, 2023 •

edited

Loading

aw-0 commented Dec 16, 2023 •

edited

Loading

Gruce commented Jan 10, 2024 •

edited

Loading

zakarialounes commented Jan 11, 2024 •

edited

Loading

provok-me commented Jun 30, 2024 •

edited

Loading

[info] [nitro] Building Nuxt Nitro server (preset: `cloudflare-pages`)

[info] [nitro] Building Nuxt Nitro server (preset: `cloudflare-pages`)

[info] [nitro] Building Nuxt Nitro server (preset: `cloudflare-pages`)

ryoid commented Jul 24, 2024 •

edited

Loading

timpulver commented Aug 21, 2024 •

edited

Loading

sugoidesune commented Sep 19, 2024 •

edited

Loading