Error when compiling typescript in ES-only plugins that use 'unist-util-visit'

[helmturner]

I'm trying to create a plugin that is ES-only, however I keep running into errors such as the following with unist-util-visit (and it's dependency unist-util-visit-parents). Am I missing something?

node_modules/unist-util-visit/index.d.ts:27:30 - error TS2834: Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.

27 export type Visitor = import('./complex-types').Visitor

tsconfig.json

{
  "compilerOptions": {
    "target": "es2017",
    "lib": ["ESNext"],
    "experimentalDecorators": true, 
    "emitDecoratorMetadata": true, 
    "useDefineForClassFields": true,
    /* Modules */
    "module": "node16",
    "moduleResolution": "node16",
    "allowJs": true,
    "declaration": true,
    "declarationMap": true,
    "outDir": "./",
    "removeComments": false,
    "declarationDir": "./",
    "isolatedModules": true,
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "strict": true
  },
  "typeAcquisition": {
    "enable": true,
  },
  "include": [
    "src/**/*.ts"
  ],
  "exclude": [
    "node_modules",
    "**/*.d.ts"
  ],
}

package.json

{
    "name": "remark-morematter",
    "version": "1.0.0",
    "engines": {
      "node": ">=14.16"
    },
    "description": "remark plugin that extends remark-frontmatter to parse, store, and optionally validate frontmatter contents.",
    "exports": "./index.js",
    "scripts": {
      "lint": "eslint --ext .js,.ts ./",
      "test": "echo \"Error: no test specified\" && exit 1"
    },
    "eslintConfig": {
      "env": {
        "es2022": true
      },
      "parserOptions": {
        "ecmaVersion": "latest",
        "sourceType": "module"
      },
      "plugins": [
        "unicorn",
        "@typescript-eslint"
      ],
      "extends": [
        "eslint:recommended",
        "plugin:@typescript-eslint/recommended",
        "plugin:unicorn/recommended"
      ]
    },
    "repository": {
        "type": "git",
        "url": "git+https://github.com/alecvision/remark-morematter.git"
    },
    "keywords": [
        "unified",
        "remark",
        "remark-plugin",
        "plugin",
        "mdast",
        "markdown",
        "frontmatter",
        "validate",
        "yaml",
        "toml"
    ],
    "author": "Alec Helmturner <[email protected]>",
    "license": "MIT",
    "bugs": {
      "url": "https://github.com/alecvision/remark-morematter/issues"
    },
    "homepage": "https://github.com/alecvision/remark-morematter#readme",
    "devDependencies": {
        "@typescript-eslint/eslint-plugin": "^5.30.5",
        "@typescript-eslint/parser": "^5.30.5",
        "eslint": "^8.19.0",
        "eslint-plugin-unicorn": "^43.0.0",
        "remark-frontmatter": "^4.0.1",
        "unified": "^10.1.2",
        "unist-util-visit": "^4.1.0",
        "vfile": "^5.3.4"
    }
  }

[ChristianMurphy]

Not surprising, this seems related to syntax-tree/hastscript#16
The community has been holding off for a bit while TypeScript stabilizes node style ESM resolution, from the last discussion:

I’ll close this for now, as it seems [typescript] reverted [node12 resolution]. PR welcome if they land this again.

• Dynamic import issue for TypeScript 4.5.0-beta "module" of "nodenext" or "node12" hastscript#16 (comment)

From what I'm seeing in the TS docs it looks like node16 support is still considered nightly (pre-beta and unstable)

node16/nodenext (nightly builds)

https://www.typescriptlang.org/tsconfig#node16nodenext-nightly-builds

[helmturner]

Wow thanks so much for the quick solution... changing to "moduleResolution": "node" in tsconfig.json took care of it.

I feel like the module nightmare is probably scaring so many potential JS devs away 😞