Geoffrey Booth

> `import.meta.resolve` is not available in CJS modules. `pathToFileURL(require.resolve('bare-specifier'))`

> `require.resolve` returns the value for the `"require"` condition of the `"exports"` map, while `import.meta.resolve` returns the `"import"` condition. Yeah. And if that’s the case for a particular package, then...

First I think we need to see if it solves the issue. If it doesn’t, there’s no point in debating whether it’s desirable UX. The thinking was that we don’t...

> Not possible during sync operations ( module.register, import.meta.resolve, faux-CJS). Can we error on sending a cross thread message while the main thread is blocked? So that we throw rather...

Is this still an issue, or has it been fixed by https://github.com/nodejs/node/pull/52706? (Try on latest `main`.)

[The `packageManager` field is still experimental](https://nodejs.org/docs/latest/api/packages.html#packagemanager) and subject to breaking changes. It’s also intended for Corepack’s internal use, not as a field for other tools. Perhaps pnpm could instead implement...

pnpm is welcome to implement the [`devEngines` field](https://github.com/openjs-foundation/package-metadata-interoperability-collab-space/issues/15). It includes two things that I think would help in this situation: - Support for semver ranges - The ability for the...

@nodejs/npm

I just discovered this issue. Here’s what I’m currently doing; I’d love to be able to do this with `zlib` instead. My use case is generating a .zip file for...

For me this feels like a missing feature that we should add. We have utilities for all sorts of compression and decompression algorithms in `zlib`; I thought for quite a...