Andy Wermke

Hey @dsl101. I wish I could be more helpful, but those webpack issues, esp. in very complex setups, are just so hard to debug. I don't have an idea off...

Thanks, @Slapbox! Yeah, sounds like webpack ends up in some kind of infinite loop while compiling and then runs out of memory. There is to little information, though, to tell...

Not sure if `esnext` is maybe a bit much as it's a moving target. Any reason not to target a specific language version, like `es2020`?

Yes, but my point is that this is a library and this configuration determines what we ship to the user. So what are we going to tell the users what...

Thanks so much for your help, @aminya! 🥳 PS: Please always share your view on things if you don't agree with me. Not sure what your current thoughts on ESNext...

I merged #351. If you rebase (or merge into) this PR, I can merge it, too 👍

I don't think node.js is ok with ES2020 😉

[ES2017 is safe](https://node.green/#ES2017). [ES2018 is not safe](https://node.green/#ES2018) to use with node 10.

Ohh, I see. Just merged and published `puppet-run`. Man, you are so quick! Thanks for all your efforts 👍 😊

Sorry, just saw that I didn't reply yet. I am a bit puzzled regarding this statement: > I forced a timeout of 100ms in spawn, which causes the expected error....