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
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? 😅
The text was updated successfully, but these errors were encountered:
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? 😅
The text was updated successfully, but these errors were encountered: