Bug: Error when using pnpm with package.yaml, 'type: module' not recognized about typescript-eslint HOT 4 CLOSED

they require their config file and rely on Node to figure out whether it is CJS or ESM code.

Almost correct they import() it. But same same. They rely on node to figure it out yeah - so if node isn't picking up your package.yaml then that's a node thing. Node defaults to assuming that .js files are cjs if it can't find a package json

An explicit mjs extension will circumvent node's assumption.

There's no bug here! Node just doesn't support a yaml file so you need to be explicit to work around that.

from typescript-eslint.

package.yaml

Well, there's the issue. It's super unusual in the Node ecosystem to use any file other than package.json there. We certainly don't support it.

In fact, the errors you're getting are from Node.js, not us!

SyntaxError: Cannot use import statement outside a module
    at internalCompileFunction (node:internal/vm:128:18)

from typescript-eslint.

We are not the ESLint project - they live over at https://github.com/eslint/eslint.

Though this stack trace isn't an ESLint error - it's straight from nodejs. So it isn't eslint's fault - Node is erroring because it is not respecting the package.yaml. AFAIK nodejs doesn't support a yaml file - only a json file.

Regardless. This is nothing to do with our project.

from typescript-eslint.

Thank you, @JoshuaKGoldberg and @bradzacher, for looking into this and for the clarification. I'm aware that you're not ESLint ;-) but didn't know on which layer in the stack the issue occurs and didn't dive deep enough to find out, sorry for that and for addressing the issue in the wrong place. I'm also aware that package.json is the default and tried to use package.yaml for the first time myself.

I was hoping for pnpm to be the only layer dealing with package.json/yaml. Since tsc and prettier both work fine and eslint-typescript deals with the module system, I got here.

If I understand correctly, they require their config file and rely on Node to figure out whether it is CJS or ESM code. Do you think it makes sense to recreate this issue in the ESLint repo?

from typescript-eslint.