Fix import with wrong extension

[nicolo-ribaudo]

Q	A
Fixed Issues?	Fixes #1, Fixes #2
Patch: Bug Fix?
Major: Breaking Change?
Minor: New Feature?
Tests Added + Pass?	Yes
Documentation PR Link
Any Dependency Changes?
License	MIT

This is a .js file. It's unfortunate that neither ESLint's import plugin neither TS complain.

[babel-bot]

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

[JLHwung]

The import/no-unresolved rule is disabled by default, since it requires a custom import resolver, so the eslint-plugin-import can't do much here. We can create own own rule just to disable vendor/**/*.ts imports. I think tsc should have warned though, at least for non-type imports.

[nicolo-ribaudo]

@JLHwung Now that we use paths with the full extension, import/no-unresolved works without a custom resolver :) It properly complain if I use the .ts extension here, while accepting .js.

[JLHwung]

Well it seems that it can't resolve relative path without further config.

[nicolo-ribaudo]

The problem is that file is auto-generated by make build, but CI artifacts do not contain auto-generated files from the src folder. It's just a special case, and the rule is working everywhere else 😬

[JLHwung]

The problem is that file is auto-generated by make build, but CI artifacts do not contain auto-generated files from the src folder. It's just a special case, and the rule is working everywhere else 😬

👍 In that case we should add it to the artifacts:

https://github.com/babel/babel/blob/56713333bea8eae3ed022aba93a6b0541dab4c0c/scripts/get-artifact-files.sh