Support latest versions of node

[hpx7]

Is your feature request related to a problem? Please describe.

I need some newer node features, mostly around ESM and loaders. My app's minimum node requirement is 15.0.

Describe the solution you'd like

Support for node v15 or v16.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any context or screenshots about the feature request here.

[trentprynn]

I would also very much like a way to configure the nodejs version used by the stackblitz webcontainer. Currently I primarily use stackblitz as a way to share bug reproductions (it's awesome, thank you!) and I'm having a problem I'm relatively sure is related node 16 that I cannot reproduce / share because stackblitz (as far as I can tell) only allows you to use node 14

[markwhitfeld]

@hpx7 I am in the process of adding this support to StackBlitz v1 right now. I will keep you posted.

@trentprynn I think that it would be best to log this issue under https://github.com/stackblitz/webcontainer-core. This is the primary place that we track the webcontainer feature requests and issues.

[blittle]

At Shopify we heavily use https://hydrogen.new for sharing and promoting the Hydrogen Framework. We recently made changes that require Node v16.5.0 or greater. If there's no way to configure stackblitz to use Node 16, we'll probably revert those changes until this issue is resolved.

[markwhitfeld]

I am closing this issue in favour of stackblitz/webcontainer-core#560

StackBlitz V1 does not run node, but provides an in browser javascript execution environment for well known project types.
We have recently added the ability for StackBlitz V1 to support ESM and the package.exports field for node packages.

StackBlitz V2 (WebContainers), on the other hand, runs a full node execution environment in the browser, and as tracked in the issue above (in the repo where issues for WebContainer are tracked), support for Node 16 is currently WIP and will be landing this quarter. There is custom work required with every release of Node due to the changes in the underlying internal APIs and feature set offered. Keeping up with Node is a constant activity for the team.