Bjorn Lu
Bjorn Lu
Would be great if you can share an example here, otherwise I'm not sure what to fix for this issue.
Ah ok I found the issue. On this line: https://github.com/bluwy/publint/blob/7ba9aa3ebd664a75044125f0ff62a28292c63308/pkg/src/index.js#L622-L623 If the path is not lintable (which simply means if it's not .js, .cjs, .mjs), it should continue to check...
Tried to repro this today and it works ootb for me. From the error logs, it looks like the packages weren't prebundled, but this shouldn't be the case now as...
I think the issue Sapphi brought up still exists, but it doesn't look like it'll be solved soon and it's probably ok still if we merge this as the errors/warnings...
Pushed a commit to migrate `eslint-plugin-i` to `eslint-plugin-import-x` (the successor), which has better eslint v9 support so the CI shouldn't fail now.
The link is not a repro: https://antfu.me/posts/why-reproductions-are-required#reproducible-projects-or-playgrounds
Seems to be related to https://github.com/vitejs/vite/pull/15585
Hmm we don't really explicitly support JSX in config files and I don't think we should fix any edge case related to it. Otherwise it'll be hard to move to...
The flaky CI fails is happening in main too. I'm investigating this and will submit a fix later. Merging this for now.
If you want to upgrade esbuild now for your project, you can use [overrides](https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides). This would be updated in the next minor.