missing main field in package.json

[CircleCode]

your package seems to fail resolution with eslint because it lacks a main field in package.json.

For example, on @tinyhttp/content-disposition, package.json should include "main": "./dist/index.js",

without the main field, normal imports do not work:

import { contentDisposition } from "@tinyhttp/content-disposition"; //eslint cannot find the module

but the following works:

import { contentDisposition } from "@tinyhttp/content-disposition/dist";

[CircleCode]

see import-js/eslint-plugin-import#2132 for eslint point of view:

A package just for the browser still needs node behavior, even if that’s “nothing”, so having it lack a main is a bug.

[talentlessguy]

"main" field is for CommonJS

tinyhttp is ESM-only and uses "exports" instead.

so not planning on returning "main" back, it's an eslint-plugin-import issue not tinyhttp's, sorry :c

[CircleCode]

for future reference (I adhere to your point of view), there are issues on eslint-plugin-import to support exports:

• no-unresolved is not aware of exports definition in package.json import-js/eslint-plugin-import#1810
• Support for package.json exports and imports ? import-js/eslint-plugin-import#1868