Sounds like a good plan to me 😄
Sounds like a good plan to me 😄
was so happy to finally figure that out 😅
was so happy to finally figure that out 😅
basically the easy part is showing dependency analysis things (dep count, install size, dupes, unmaintained, redundant etc). but there's much more than that
basically the easy part is showing dependency analysis things (dep count, install size, dupes, unmaintained, redundant etc). but there's much more than that
often we measure the framework in isolation but not a typical project. there's a lot of useful metrics even before we try measure raw perf
often we measure the framework in isolation but not a typical project. there's a lot of useful metrics even before we try measure raw perf
initially it may mean building the foundations w/ me until others can join
happy to try explain this better in discord or DM too
initially it may mean building the foundations w/ me until others can join
happy to try explain this better in discord or DM too
- CLI to detect and auto-migrate replacements, polyfills, etc
- GitHub actions (e.g. the dependency diff action)
- MCP server
future areas: framework perf tracking, npm data analysis, compat data
- CLI to detect and auto-migrate replacements, polyfills, etc
- GitHub actions (e.g. the dependency diff action)
- MCP server
future areas: framework perf tracking, npm data analysis, compat data
most of the size was from the CLI framework
most of the size was from the CLI framework
the only way you can get this to work is by running the typescript, which means changing all your project's imports to `.ts`
incorrectly because this project isn't built for engines that natively run ts, the imports should be .js
the only way you can get this to work is by running the typescript, which means changing all your project's imports to `.ts`
incorrectly because this project isn't built for engines that natively run ts, the imports should be .js