You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to propose a linting plugin that builds on top of BundlePhobia's alternative package recommendations.
I believe this would improve awareness and adoption of small packages. It would also form a nice bridge between this project and other common entry-points for building webapps (e.g package manager CLIs, framework CLIs, bundlers etc).
Describe the solution you'd like
It would be really powerful if there was a BundlePhobia webpack, babel or ESLint plugin that could lint for usage of popular large dependencies and suggest alternatives. Something that could potentially integrate with an npm/yarn preinstall step so maybe even recommendations are made before users perform an install.
Something like:
$ npm install moment
$ > bundle-lint found 3 smaller alternatives for your consideration.
> How would you like to proceed?
[ ] install luxon [19.29KB min/gzip - 71% smaller]
[ ] install date-fns [2.74KB min/gzip - 90% smaller]
[ ] install dayjs [6.54KB - 90% smaller]
[ ] install moment
(could even include brief notes on which support timezones/locales)
There are also lots of directions one could take linting - you could scan their source/package.json to understand if there are specific features in moment being used and suggest the best "fit", saving the author from more research before making a decision.
$ npm install moment
$ > bundle-lint found 3 smaller alternatives for your consideration.
> How would you like to proceed?
[ ] install luxon [19.29KB min/gzip - 71% smaller] - recommended (closest match for you)
[ ] list more alternatives
[ ] install moment
Describe any alternatives you've considered
Alternatives today include using ESLint and the no-restricted-imports rule to disallow known large imports. This often ends up a manually curated effort however. I think BundlePhobia is in a good position to offer a data-driven solution to this problem... :)
The text was updated successfully, but these errors were encountered:
Please describe the feature/suggestion
I would like to propose a linting plugin that builds on top of BundlePhobia's alternative package recommendations.
I believe this would improve awareness and adoption of small packages. It would also form a nice bridge between this project and other common entry-points for building webapps (e.g package manager CLIs, framework CLIs, bundlers etc).
Describe the solution you'd like
It would be really powerful if there was a BundlePhobia webpack, babel or ESLint plugin that could lint for usage of popular large dependencies and suggest alternatives. Something that could potentially integrate with an npm/yarn preinstall step so maybe even recommendations are made before users perform an install.
Something like:
(could even include brief notes on which support timezones/locales)
There are also lots of directions one could take linting - you could scan their source/package.json to understand if there are specific features in moment being used and suggest the best "fit", saving the author from more research before making a decision.
Describe any alternatives you've considered
Alternatives today include using ESLint and the no-restricted-imports rule to disallow known large imports. This often ends up a manually curated effort however. I think BundlePhobia is in a good position to offer a data-driven solution to this problem... :)
The text was updated successfully, but these errors were encountered: