-
Notifications
You must be signed in to change notification settings - Fork 60
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
Help with updating plugin library dependencies properly in Node 22+ #604
Comments
I'll take a look later this week |
Thanks @aaronpoweruser |
Result of (node:21902) ExperimentalWarning: CommonJS module /opt/homebrew/lib/node_modules/npm/node_modules/debug/src/node.js is loading ES Module /opt/homebrew/lib/node_modules/npm/node_modules/supports-color/index.js using require(). |
I can do this fairly quickly so I'll put up a PR. My question is if people would prefer switching to a different package manager for the repo? Both The counter-point is that Bun on Windows is somewhat new and it's another new thing for people to install. |
#606 created |
@nmn I think we're open to your advice on the package manager. We can adapt
to anything, and there are not that many of us. Nobody on Windows so that
is not a limitation.
ᐧ
…On Wed, Dec 4, 2024 at 1:55 PM Naman Goel ***@***.***> wrote:
I can do this fairly quickly so I'll put up a PR. My question is if people
would prefer switching to a different package manager for the repo?
Both pnpm and bun are significantly faster and generally more reliable. I
recommend switching to bun for this repo instead of Node. Bun is
essentially a drop-in replacement for Node but it uses the JavasrciptCore
JS engine instead of V8. This is the same engine that Noteplan uses
internally and so should work more reliably.
The counter-point is that Bun on Windows is somewhat new and it's another
new thing for people to install.
—
Reply to this email directly, view it on GitHub
<#604 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACEI6VDUT7KGN4OQI2UWGSL2D5237AVCNFSM6AAAAABS36QZZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJYGYZTSNRYGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
@dwertheimer I will try to do a big improvement to the setup sometime soon then. There should be fewer dependencies and everything should compile faster. I also think it would be useful to switch from Flow to Typescript just because that is the industry standard now. Anyway, if it's too much work, I'll bail! |
@nmn Thanks so much. This all looks good. The plugins all build and the tests all pass. Of course we don't have near 100% coverage, but it all seems good to merge when you are ready. Fingers crossed on all of this! |
I've switched to node 22 and then
I've had a go at fixing this, but its saying its a deprecated package, and I'm beyond my limited understanding. |
@jgclark Go to This dependency was removed because |
Thanks, @nmn. I'd not wanted to do that as I could see that the terser was being used in |
We have reached a point where our project dependencies will no longer load properly with a standard
npm i
. In order to get the modules to load with their dependencies, we have to enternpm i --legacy-peer-deps
. This is obviously a band-aid and needs to be fixed. This is outside of my node/coding level expertise. @nmn or anyone else listed here, can you help upgrade the codebase?The text was updated successfully, but these errors were encountered: