* added Error 5084 to diagnosticMessages.json * added test case errorForBareSpecifierWithImplicitModuleResolution1 to tests/cases/compiler * modified checker.ts to report error 5084 when classic resolution and incorrect path are used * added baseline changes * passes all test cases including src/testRunner/unittests/ tests * Update with feedback * Make it check whether it is the right module resolution kind * Use the right diagnostic message in tsserver tests Co-authored-by: Meera Shivakumar <mshivaku@umich.edu> Co-authored-by: Orta <git@orta.io>
18 lines
1.5 KiB
Plaintext
18 lines
1.5 KiB
Plaintext
tests/cases/conformance/externalModules/esnext/esnextmodulekindWithES5Target10.ts(1,1): error TS1202: Import assignment cannot be used when targeting ECMAScript modules. Consider using 'import * as ns from "mod"', 'import {a} from "mod"', 'import d from "mod"', or another module format instead.
|
|
tests/cases/conformance/externalModules/esnext/esnextmodulekindWithES5Target10.ts(1,20): error TS2792: Cannot find module 'mod'. Did you mean to set the 'moduleResolution' option to 'node', or to add aliases to the 'paths' option?
|
|
tests/cases/conformance/externalModules/esnext/esnextmodulekindWithES5Target10.ts(6,1): error TS1203: Export assignment cannot be used when targeting ECMAScript modules. Consider using 'export default' or another module format instead.
|
|
|
|
|
|
==== tests/cases/conformance/externalModules/esnext/esnextmodulekindWithES5Target10.ts (3 errors) ====
|
|
import i = require("mod"); // Error;
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
!!! error TS1202: Import assignment cannot be used when targeting ECMAScript modules. Consider using 'import * as ns from "mod"', 'import {a} from "mod"', 'import d from "mod"', or another module format instead.
|
|
~~~~~
|
|
!!! error TS2792: Cannot find module 'mod'. Did you mean to set the 'moduleResolution' option to 'node', or to add aliases to the 'paths' option?
|
|
|
|
|
|
namespace N {
|
|
}
|
|
export = N; // Error
|
|
~~~~~~~~~~~
|
|
!!! error TS1203: Export assignment cannot be used when targeting ECMAScript modules. Consider using 'export default' or another module format instead. |