Is there a reason why npm packages should not target the highest possible target that an LTS Node.js supports? On the front-end those that need lower targets wi

Is there a reason why npm packages should not target the highest possible target that an LTS Node.js supports? On the front-end those that need lower targets will run their own transpiling anyway to whatever target they want. I'm about to release a few simple npm packages and I'm considering ES2017 as the target (since it has the last major feature - async / await). I'm guessing it's just that the end-user of the library would need to be aware of the polyfills that need to be supplied. I have asked a question [0] about it a while back but it did not get any responses. To clarify - the goal is if you have a project that uses ES7, why would you want to use a package written in ES2020 that is transpiled to, i.e. ES2016 using non-native async / await. [0] https://stackoverflow.com/questions/76558023/whts-the-ideal-es-target-for-an-npm-package https://stackoverflow.com/questions/76558023/whts-the-ideal-...