Starting SW building... Could not resolve v13

[okpierre]

💡 Summary

│ Error: Build failed with 5 errors:
│ src/filters/user.ts:2:22: ERROR: Could not resolve "misskey-js/built/acct"
│ src/scripts/get-account-from-id.ts:1:20: ERROR: Could not resolve "idb-keyval"
│ src/scripts/lang.ts:4:25: ERROR: Could not resolve "idb-keyval"
│ src/scripts/notification-read.ts:1:20: ERROR: Could not resolve "idb-keyval"
│ src/scripts/operations.ts:5:25: ERROR: Could not resolve "misskey-js"

🥰 Expected Behavior

No build errors for new install

🤬 Actual Behavior

all the errors https://pastebin.com/u8PzTeiH

📝 Steps to Reproduce

1. follow installation docs
2. errors during build process

📌 Environment

Misskey version: v13 https://github.com/misskey-dev/misskey/commit/9d64ac6d6f4050b260d1a3ff39efbd932f4a523f Your OS: Ubuntu Linux VPS 2GB memory

[tamaina]

follow installation docs

The installation doc is useless because they still use yarn.
https://misskey-hub.net/en/docs/install/manual.html

Please use pnpm instead of yarn.

[tamaina]

I updated misskey-hub.

[Sakrecoer]

Thank you @tamaina! Wouldn't the systemd service also need to refer to pnpm? Currently it shows ExecStart=/usr/bin/npm start

[tamaina]

Wouldn't the systemd service also need to refer to pnpm?

Either npm or pnpm may be acceptable...I do not have a clear answer.

[yitsushi]

Can be related: https://github.com/misskey-dev/misskey/issues/9328#issuecomment-1504435146

[KisaragiEffective]

triage: we use pnpm in recent releases.