Open kravetsone opened 3 months ago
I think it could be interesting if included in core, but perhaps at a later time once I finished building a plugin API so it can be experimented as a plugin first. It would indeed be controversial, but I think it has some value to push towards publishing leaner dependencies. I'll mark this as a future enhancement for now.
I think it could be interesting if included in core, but perhaps at a later time once I finished building a plugin API so it can be experimented as a plugin first. It would indeed be controversial, but I think it has some value to push towards publishing leaner dependencies. I'll mark this as a future enhancement for now.
Great! I am glad how we aim for a better future) Also thanks for the post about my extension repository) I was very surprised and glad!
What if
publint
suggests to replace dependencies as part of e18e.dev? (I know that @bluwy is already taking the initiative there)I think this is something that
publint
could do (although it may be quite controversial), but it would help developers to notice more dependencies that need to be replaced without usage of eslint plugins and etcI think it would also look good in an publint VS Code extension
I understand that perhaps
publint
has slightly different goals, but it could be usefulsimilar: es-tooling/module-replacements es-tooling/eslint-plugin-depend danielroe/unplugin-purge-polyfills