Maël Nison

`corepack up` is meant to update the version of the `packageManager` field. In a sense it's similar to what would be `install` without the `-g` flag, but without needing the...

Corepack is still experimental, so a regression in that way isn't necessarily to be fixed. Especially the part about "Yarn to the latest 1 and everything else to the latest...

Fyi, the easiest no-config way to detect whether Plug'n'Play should be enabled or not is to simply check whether you're running under it or not. This can be easily checked...

As mentioned in https://github.com/ember-cli/ember-try/issues/214#issuecomment-437022648, you might be interested in `process.versions.pnp` to check whether PnP is enabled or not 😃

> which definitely are not overridden by an in-scope `n` variable Why is that? It's not clear to me why they would behave so differently from template functions. Is the...

Thanks for the example, it's clearer now! That being said, while I see the concern, it feels somewhat low compared to adding a whole different syntax. You say it'd be...

On top of the `eval` issue, I saw the following note: ``` "Worker.ref()" is not yet implemented. Please file an issue on GitHub if you rely on this feature. ```...

Thanks for the speedy improvements, Jasper! > Wouldn't `events.once` cover that? I meant that "wait for a process to exit before spawning another" is a common enough need (especially given...

Quick note: I noticed there's been a regression that makes `new URL('npm:1.2.3').pathname === "//1.2.3"`, instead of `"1.2.3"`: https://codesandbox.io/p/sandbox/vanilla-nodebox-forked-uhqmt1

Indeed! And I see you've started to implement worker support, very nice 👍 I think we're now hitting the problem in https://github.com/codesandbox/nodebox-runtime/issues/22#issuecomment-1457951172: `eval: true` as worker parameter is ignored, so...