SolidStart ver.1
everytime I come to test solid, I'm met with issues out-of-the-box
Also and Sorry to rant, but everything needs to be looked at.
So much junk in the add on libraries or plugins.
Does it work, no - do we need it? no get rid of it, yes fix it.
Please start paying a team if you can't cope.
Picture is ss1 notes js
9 Replies
SolidStart builds on top of Vinxi which sits on top of Nitro/Vite which are maintained by other teams. The
nitropack (Nitro) pulls in @vercel/nft which is pulling in @mapbox/node-pre-gyp which pulls in npmlog etc, so not to come with excuses, but some of these issues likely better to resolve upstream by the Nitro, Vercel or Mapbox team.
glob 7.2.3 is also from @vercel/nft, so that seem to account for multiple of issues, so maybe that's a good place to put a ticket, or maybe nitro can use an alternative dependency.There is a ticket here for most of these issues
https://github.com/vercel/nft/issues/421
GitHub
Deprecated subdependencies found in @mapbox/node-pre-gyp · Issue #4...
Description When installing dependencies for our project that uses @vercel/nft, we encountered warnings about deprecated subdependencies. These warnings are caused by the @mapbox/node-pre-gyp packa...
Simple tipp for new developers:
just dont use npm
-> use pnpm or bun instead
No single developer working on bigger projects still uses npm
How does pnpm solve deprecated subdependencies?
I do. Works great.
Same as (or better as) npm
No single developer working on bigger projects still uses npmJust want to say that this is wholely untrue – although I do recommend using yarn or pnpm instead. Most people use what comes out of the box and is the most recommended and familiar, which is
npm
pnpm does not solve deprecated (sub)dependencies (neither does yarn, bun, or anything else). They just aren't calling out those issues
pnpm's main feature is that it saves disk space by using a different cache and linking strategy that npm lacks.
yarn has a "pnp" strategy that does some huge efficiencies in space saving and ensuring package version lock, but I've not seen any major teams really using it, due to the host of problems it tends to create. yarn does, however have a better resolution algorithm, monorepo support, and plugins out of the box (like it will auto install @types/ packages when necessary)Yarns 2.0+ and everyhting "pnp" has never worked for me (last try in 2023), especially with libraries like prisma, next or vite that rewrite the content in node_modules.
I do not know anyone who uses yarn 2.0+, only people who still use yarn 1.0 and did not bother to update (or tried an failed).
yarn "have a better resolution algorithm, monorepo support, and plugins out of the box"
-> only if compared to npm (because npm is the worst package manager, currently)
-> against pnpm its worse (by my knowledge)
I use Yarn with prisma, vite, and everything else with teams of varying sizes and many projects for years. No problems
Just don't use yarn's "pnp" … it's just too flawed