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

Status in 2021? #1

Open
fgblomqvist opened this issue Sep 9, 2021 · 0 comments
Open

Status in 2021? #1

fgblomqvist opened this issue Sep 9, 2021 · 0 comments

Comments

@fgblomqvist
Copy link

Hey, I think this is a pretty good idea and I am baffled by how package.json doesn't currently have a way of showing what version you publish your code in. Even something simple as a blanket "my lib is ES5". Neither is it a convention to even mention in your docs what version you publish your lib in. If you as a user want to know, you have to dig into the source to find any target configs/build setups etc. (can be really tedious).

It seems to me that everyone is just riding on the hopeful scenario that every lib you use will work for the browsers/clients you wanna support 😕

I'm pretty sure there's a vast majority of developers out there that don't even know whether their web framework transpiles node_modules or not (from my findings, it seems like CRA might have at one point (v2) but unclear if it still does, Nextjs does not, and Vitejs idk).

If the standard was to always transpile your 3rd-party modules I could understand why people don't specify things in their libs, but afaik, the general recommendation (e.g. by babel) seems to be to not do so due to expensiveness.

So, how come something like your proposal hasn't materialized or gained traction? Am I missing something that happened after your proposal was written? 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant