@TheAlexLichter@evanyou yep that solved the immediate problem. but there's also multiple copies of rolldown, oxc types, pluginutils, due to 1st party libs like plugin-babel pinning specific versions. been wishing vite, vitest, oxc, rolldown, plugins, etc. get versioned together / bundled 🥺.
@TheAlexLichter@evanyou due to the way pnpm 10 resolve peer deps, a random deep transitive dep declaring @types/node: '*' created multiple subtrees of voidzero-dev+vite-plus-test. pnpm 11 with aggressive dedupe may help, but declaration merging across modules is still fragile esp w/ lots of reexport
@tannerlinsley been using ts router for months & it's awesome! couldn't on-shot migrate this 3-years-old nextjs blog project though. it kinda falls into the sweet spot with pages router & getStaticPaths(). love to see what we can do!
https://t.co/ZkDMLIMVG0
@saltyAom btw is there anyway to dynamically add & remove routes with staticPlugins in elysia? need that to build a route-based preview deployment server. wildcard routes exist but nullifies the purpose of using a good router lib like elysia.
@tan_stack OMG these are the exact features I dreamed for when building apps. Looked for real type-safe hotkey manager libs to no avail and now here it is!
@TheAlexLichter one big challenge tho is oxfmt vscode extension can't format JSON, YAML, TOML, and CSS on save or on type just yet, making it necessary to add a .prettierrc nonetheless to prevent prettier from messing things up :(
@pnpmjs@wojtekmaj91 Suggestion: "no degrade" might be clearer than "no downgrade". Most devs hear "downgrade" and immediately think of package versions (e.g., v2.0 → v1.0).
Would "no degrade" be more precise for this context?