Bjorn Lu

Yeah I was thinking there would be an opt-in option to tell publint that this package, by default, works with bundlers/node/browser only. And if the option is not specified, it...

That's a good idea. The main concern I had was server costs as this means downloading arbitrary packages on the server-side, which instead I opt-ed to run publint on the...

Hi, yeah this is something not implemented yet as the tool doesn't scan for imports recursively. That can only be done once https://github.com/bluwy/publint/issues/13 is started. It's something I want to...

Initial attempt at https://github.com/bluwy/publint/tree/fix-typesVersion

Published v0.1.13 with a patch to ignore the error for now if `"typesVersions"` exist. Might return in making the resolution work again in the future, so leaving this open.

Awesome! IIRC the resolver for `typesVersion` was really complex and not comprehensively documented, and it was hard to portray an error for multiple specified TypeScript versions. But otherwise if anyone...

Gave an attempt at https://github.com/bluwy/publint/tree/umd-suggestion. Also updated the description about named imports interop. It seems to affect IIFE specifically, not UMD.

I probably need some time to think about this, as right now `publint` focuses on JS file syntax and exports. Expanding to `dependencies` checking could be nice as a "publish...

Looks like it's happening since Deno is using strict hoisting installation in `node_modules`. Pretty sure it works with pnpm though, so I'm not sure why Deno is having this issue....

There's also a similar issue open in Vite recently without Deno: https://github.com/vitejs/vite/issues/13129. Not sure if it's related. There's also this Deno issue which seems to be the same: https://github.com/denoland/deno/issues/16653. The...