Boshen

``` blueprint  develop ❯ ~/github/oxc/target/release/oxlint --import-plugin -D named ⚠ eslint-plugin-import(named): named import "default" not found ╭─[packages/karma-build-scripts/index.mjs:7:10] 6 │ 7 │ export { default as createKarmaConfig } from "./createKarmaConfig.mjs"; ·...

@Dunqing What should be the best way to fix this? Save all the export names for TypeScript types?

`export type * from "mod"` doesn't fix the error 😅

> > ``` > > ⚠ eslint-plugin-import(export): Multiple exports of name 'TimePrecision'. > > ╭─[packages/datetime/src/index.ts:29:10] > > 28 │ export type { TimePickerProps } from "./common/timePickerProps"; > > 29 │...

> > @Dunqing What should be the best way to fix this? Save all the export names for TypeScript types? > > Yes, it seems we must. But after doing...

https://github.com/rolldown/rolldown/actions/runs/8968666129/job/24628561631?pr=1027 ``` > monorepo@ lint-code /home/runner/work/rolldown/rolldown > oxlint --ignore-path=./.oxlintignore --import-plugin --deny-warnings ! eslint-plugin-import(named): named import "default" not found ,-[examples/par-babel-rome-ts/rolldown.config.js:5:10] 4 | import nodeUrl from 'node:url' 5 | import { default...

@Dunqing I tested locally, they aren't fixed yet with ` --ignore-path=./.oxlintignore --import-plugin --deny-warnings` https://github.com/rolldown/rolldown/actions/runs/9011082137/job/24758169189?pr=1065

Is this resolved?

> What scope info transformers need. All we need are the scope flags. During traversing, we keep a stack of scopes, and manage binding information while entering / leaving scopes....

I need to store things associated with a scope, but I think I can work with what you proposed to get things started.