Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publint suggestions to replace dependencies #98

Open
kravetsone opened this issue Jun 29, 2024 · 2 comments
Open

Publint suggestions to replace dependencies #98

kravetsone opened this issue Jun 29, 2024 · 2 comments
Labels
future enhancement New feature or request but maybe for the future

Comments

@kravetsone
Copy link

What if publint suggests to replace dependencies as part of e18e.dev? (I know that @bluwy is already taking the initiative there)

The e18e project is an initiative to bring together the groups and individuals who are passionate about improving performance of the JavaScript ecosystem.

Many ongoing efforts are already happening in this space, from dependency tree cleanups to performance optimizations, and much more.

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 etc

I think it would also look good in an publint VS Code extension

image

I understand that perhaps publint has slightly different goals, but it could be useful

similar:
es-tooling/module-replacements
es-tooling/eslint-plugin-depend
danielroe/unplugin-purge-polyfills

@bluwy
Copy link
Owner

bluwy commented Jun 29, 2024

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.

@bluwy bluwy added the future enhancement New feature or request but maybe for the future label Jun 29, 2024
@kravetsone
Copy link
Author

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future enhancement New feature or request but maybe for the future
Projects
None yet
Development

No branches or pull requests

2 participants