ESLint Warning n/no-missing-import

[danielpeintner]

With #1424 we introduced some new eslint warnings.

One warning is n/no-missing-import

node-wot/eslint.config.mjs

Lines 79 to 82 in 736f280

	// relax missing import rule to warning, as we sometimes have optional dependencies
	// import "../foo" will braise a warning ,
	// import "../foo.js" is the correct way to import a file that may not exist
	"n/no-missing-import": "warn",

Which shows for normal imports like

node-wot/packages/core/src/codecs/base64-codec.ts

Line 16 in 736f280

import { ContentCodec } from "../content-serdes";

To fix it (as the comment above alludes), one needs to change

import { ContentCodec } from "../content-serdes";

to

import { ContentCodec } from "../content-serdes.js";

Do we really want to do that? I think it works but to me, it looks somewhat silly in a TS project to reference JS files?

Opinions?

[erossignon]

The main benefit will be to allow node-wot to prepare for esm migration (as opposed to commonjs)

https://www.typescriptlang.org/docs/handbook/modules/theory.html#module-resolution#relative-vs-non-relative-module-imports

I would turn this rule to off "n/no-missing-import": "off", for the time being, unless we have a plane to create a ESM flavored version of Node-Wot.

[danielpeintner]

I would turn this rule to off "n/no-missing-import": "off", for the time being, unless we have a plane to create a ESM flavored version of Node-Wot.

Fine by me.
@relu91 @egekorkan any opinion?