Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL  misskey-js@0.0.15 build: tsc #10957

Open
MomentQYC opened this issue Jun 5, 2023 · 9 comments
Open

ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL  misskey-js@0.0.15 build: tsc #10957

MomentQYC opened this issue Jun 5, 2023 · 9 comments
Labels
⚠️bug? This might be a bug

Comments

@MomentQYC
Copy link
Contributor

💡 Summary

After upgrading to Misskey 13.13.0, using the NODE_ENV=production pnpm run build command throws an exception
No changes to any files in packages/misskey-js

🥰 Expected Behavior

Normal build

🤬 Actual Behavior

Unable to build

Scope: 4 of 5 workspace projects
packages/misskey-js build$ tsc
│ node:internal/modules/cjs/loader:1078
│   throw err;
│   ^
│ Error: Cannot find module ' /path/to/misskey/node_modules/.pnpm/typescript@5.0.4/node_modules/typescript/bin
│     at Module._resolveFilename (node:internal/modules/cjs/loader:1075:15)
│     at Module._load (node:internal/modules/cjs/loader:920:27)
│     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
│     at node:internal/main/run_main_module:23:47 {
│   code: 'MODULE_NOT_FOUND',
│   requireStack: []
│ }
│ Node.js v18.16.0
└─ Failed in 122ms at /path/to/misskey/packages/misskey-js
/path/to/misskey/packages/misskey-js:
 ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL  misskey-js@0.0.15 build: `tsc`
Exit status 1
 ELIFECYCLE  Command failed with exit code 1.

📝 Steps to Reproduce

  1. git pull
  2. git submodule update --init
  3. NODE_ENV=production pnpm install --frozen-lockfile
  4. NODE_ENV=production pnpm run build

📌 Environment

Misskey version: 13.13.0
Your OS: (Server) Ubuntu 20.04
Nodejs 18.16.0
pnpm 8.6.0

@MomentQYC MomentQYC added the ⚠️bug? This might be a bug label Jun 5, 2023
@tamaina
Copy link
Contributor

tamaina commented Jun 5, 2023

path/toは置き換えたのか

@MomentQYC
Copy link
Contributor Author

path/toは置き換えたのか

The meaning here is Misskey's folder, like /home/misskey

@tamaina
Copy link
Contributor

tamaina commented Jun 5, 2023

I can't reproduce it in the environment at hand, but I don't know why (is it possible to build?)

@tamaina
Copy link
Contributor

tamaina commented Jun 5, 2023

I'm thinking this is due to the lack of typescript, etc. in the dependencies.

@tamaina
Copy link
Contributor

tamaina commented Jun 5, 2023

In misskey-js/package.json, can you try moving typescript and @types to dependencies?

@MomentQYC
Copy link
Contributor Author

In misskey-js/package.json, can you try moving typescript and @types to dependencies?

I added "typescript": "5.0.4" to dependencies and it works fine.

@lucyrose39
Copy link

Can confirm I also have this issue with the same error, however with a server running debian 11.

@lucyrose39
Copy link

Can confirm I also have this issue with the same error, however with a server running debian 11.

Resolved by installing global typescript compiler

@iruuuuull
Copy link

iruuuuull commented Aug 8, 2024

image

how to fix this issue? already 2 day can't fix this.

This error is obtained if run with docker file.

On normal build executed successfully

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⚠️bug? This might be a bug
Projects
None yet
Development

No branches or pull requests

4 participants