Question

54

running node with loader ts-node/esm.js requires imports to have the .js extension

rated 0 times [ 60] [ 6] / answers: 1 / hits: 5973 / 4 Years ago, wed, september 9, 2020, 12:00:00

I am trying to run node 14 with my package.json set as module:

"type": "module",

If I run this command on a typescript file:

 node --loader ts-node/esm.mjs --experimental-top-level-await ./src/scripts/ts-build.ts --trace-warnings --experimental-json-modules

and I have extensionless imports like this in a typescript file

import { logger } from './logger';

I get

ERR_MODULE_NOT_FOUND

But if I change it to

import { logger } from './logger.js';

It works.

Why is this?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

isaacvalentinn

Add To Favorites

Follow

Total Points: 325

Total Questions: 120

Total Answers: 131

Location: North Korea

Member since Tue, Jun 16, 2020

4 Years ago

isaacvalentinn questions

1 BrowserAuthError: interaction_in_progress - Unable to fix, regardles of solutions found

Tue, Aug 10, 21, 00:00, 3 Years ago

1 How to transform a Luxon DateTme object to a date

Mon, Jan 18, 21, 00:00, 3 Years ago

1 __dirname is not defined

Mon, Nov 23, 20, 00:00, 4 Years ago

1 How to get status code in angular observable

Wed, Sep 23, 20, 00:00, 4 Years ago

1 Mocking Secrets Manager module for JavaScript jest unit tests

Mon, Jun 15, 20, 00:00, 4 Years ago

View All

answered 4 Years ago devonw · Accepted Answer

If we take a look at the spec there's this section which states:

The current specifier resolution does not support all default behavior
of the CommonJS loader. One of the behavior differences is automatic
resolution of file extensions and the ability to import directories
that have an index file.

There's another section which states:

A file extension must be provided when using the import keyword.
Directory indexes (e.g. './startup/index.js') must also be fully
specified.

So it seems that the extension is actually necessary. Howvever, there's the option --experimental-specifier-resolution which you try setting to --experimental-specifier-resolution=node.