With #1424 we introduced some new eslint warnings.
One warning is n/no-missing-import
|
// 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
|
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?
With #1424 we introduced some new eslint warnings.
One warning is
n/no-missing-importnode-wot/eslint.config.mjs
Lines 79 to 82 in 736f280
Which shows for normal imports like
node-wot/packages/core/src/codecs/base64-codec.ts
Line 16 in 736f280
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?