throw '"glob"' has no exported member named 'globSync'. Did you mean 'GlobSync' in 10.3.7 about node-glob HOT 5 CLOSED

Ah, actually, no, that leads to incorrect types being exported for the commonjs build, which is why tshy enforces that top level types remain unset.

Enable resolvePackageJsonExports, that is the correct way to address this.

from node-glob.

Can confirm, simply using 10.3.7 and using import { globSync } from 'glob'; causes this error. Downgrading to 10.3.6 resolves the issue.

Repro: https://codesandbox.io/p/sandbox/npm-playground-forked-ch2hmh?file=%2Findex.ts%3A3%2C7

from node-glob.

Can confirm, simply using 10.3.7 and using import { globSync } from 'glob'; causes this error. Downgrading to 10.3.6 resolves the issue.

Repro: https://codesandbox.io/p/sandbox/npm-playground-forked-ch2hmh?file=%2Findex.ts%3A3%2C7

Yes, I lock the glob version to 10.3.6 to solve this issue now. Hope to solve this problem soon!

from node-glob.

TypeScript won't enable resolvePackageJsonExports by default, but can help for now #556 (comment)

from node-glob.

I'll add the types field back in, but you really need to start doing "module": "node16" or "module": "nodeNext" in your tsconfigs, or you're almost certainly getting subtly wrong types any time you import a hybrid module, especially if you are building commonjs.

If you have that option enabled, but are still seeing these warnings, make sure that the module emitting the warning is covered by the tsconfig in question (ie, included in files or include, and not excluded by exclude options).

from node-glob.