add 12 missing NODE_FIELDS

[jedwards1211]

fix #13558
fix #13563

QUESTION: Can ExportDefaultDeclaration.exportKind be anything other than "value"? I looked through the parser code and tried to come up with Flow or TS example that would result in exportKind: "type", but couldn't find any.

Q	A
Fixed Issues?	Fixes #1, Fixes #2
Patch: Bug Fix?	Yes
Major: Breaking Change?	No
Minor: New Feature?	No
Tests Added + Pass?	Yes
Documentation PR Link
Any Dependency Changes?	Added glob and fs-extra to devDependencies of @babel/types
License	MIT

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 60f3126:

Sandbox	Source
babel-repl-custom-plugin	Configuration
babel-plugin-multi-config	Configuration

[babel-bot]

Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/47487/

[JLHwung]

I guess we can replace fs-extra by JSON.parse(fs.readFileSync(#))?

[jedwards1211]

I just switched it to promisify(fs.readFile), wouldn't want to block the entire process

[jedwards1211]

argh, didn't realize tests run on node 8 though,I'll promisify it manually

[jedwards1211]

There are lint errors I didn't cause:

Error: packages/babel-traverse/src/path/lib/virtual-types.ts(119,7): error TS2578: Unused '@ts-expect-error' directive.
Error: packages/babel-generator/src/generators/flow.ts(550,3): error TS2578: Unused '@ts-expect-error' directive.
Error: packages/babel-generator/src/generators/flow.ts(555,5): error TS2578: Unused '@ts-expect-error' directive.

[nicolo-ribaudo]

Whops thanks, I'll fix them on main. I'm surprised CI is green there.

[nicolo-ribaudo]

Can ExportDefaultDeclaration.exportKind be anything other than "value"?

No, but we still set it for consistency with the other export and import declarations.

[jedwards1211]

@nicolo-ribaudo okay, well it sets exportKind: "value" of ExportDefaultDeclarations when parsing TS, but not when parsing Flow, so I think that's a bug with parsing Flow then

[nicolo-ribaudo]

@jedwards1211 The linting failures seem to be caused but this PR, but it's a good thing since we were just telling TS "we know that our code doesn't respect the declared type, so there is an error here".

You can just delete those three @ts-expect-error comments.

[jedwards1211]

Oh now I get it, someone put those @ts-expect-errors there to suppress errors due to the missing fields...but those were valid errors...
Hopefully the fields weren't intentionally missing for some reason?

[nicolo-ribaudo]

It's just that we use Flow and TS nodes in the plugins way less than JS nodes, so we never noticed it. Thanks for this PR!