Skip to content

Update Node and switch back to pnpm#131

Merged
Protonull merged 7 commits intomainfrom
upgrade-server-env
Mar 31, 2026
Merged

Update Node and switch back to pnpm#131
Protonull merged 7 commits intomainfrom
upgrade-server-env

Conversation

@Huskydog9988
Copy link
Copy Markdown
Contributor

Upgrade to Node v24, and switch back to pnpm for better security model + caching.

@Huskydog9988 Huskydog9988 requested a review from Protonull March 30, 2026 21:35
@Protonull
Copy link
Copy Markdown
Contributor

Why the switch back to pnpm?

@Protonull
Copy link
Copy Markdown
Contributor

You'll also need to update the key-pair encryption algorithm since the security revert that permits the continued use of PKCS#1 v1.5 is gone in v24 (v18..v24). The server will start up fine but will error on any attempt to decrypt anything.

@Huskydog9988
Copy link
Copy Markdown
Contributor Author

Yea I'll update the algorithm, thought the client was broken for another reason lol. I switched back to pnpm because it drastically reduces the file size of node_modules, installing packages is faster too, (both of which benefit ci), and makes it so you can't import transitive dependencies. Plus, pnpm makes a whole bunch of improvements to the npm security model.

@Protonull
Copy link
Copy Markdown
Contributor

After discussing this in Discord, I'm going to merge this, re-open and merge #108, and then begin working on websockets.

@Protonull Protonull merged commit 4104b64 into main Mar 31, 2026
2 checks passed
@Protonull Protonull deleted the upgrade-server-env branch March 31, 2026 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants