Support TypeScript's moduleResolution: "Node16"
#524
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support for TypeScript's
moduleResolution: "Node16"
.There's more information about what this this entails in https://www.typescriptlang.org/docs/handbook/esm-node.html, but essentially, it lets TypeScript check that all ESM imports match what Node.JS can import.
However, TypeScript will no longer look at the
"types"
/"typing"
field in yourpackage.json
file. Instead, they except entries in the"exports"
field inpackage.json
.In order to avoid breaking backwards compatibility with newer versions of Node.JS, that may have use something like
import * from "@adobe/jsonschema2md/lib/config"
, we need to explicitly list every single import path that people may have used.Before
Using https://arethetypeswrong.github.io/?p=%40adobe%2Fjsonschema2md%407.1.5, we can see that the
node16
types are currently broken for@adobe/jsonschema2md
v7.1.5:After
Run
npm pack
, and upload the file to https://arethetypeswrong.github.io/