Rongjian Zhang

> This needs a rebase @aduh95 Updated

If I understand it correctly, there is a section in the [readme](https://github.com/pd4d10/vite-plugin-svgr#usage) you can refer to: > If you are using TypeScript, there is also a declaration helper for better...

`ReactComponent` named export is for v3 and prior versions. For the latest v4, please check out the document here: https://github.com/pd4d10/vite-plugin-svgr?tab=readme-ov-file#usage Background here: https://github.com/pd4d10/vite-plugin-svgr/pull/71#issuecomment-1727006445

Would [Vite glob import](https://vitejs.dev/guide/features.html#glob-import) help?

Thanks for the report. Could you provide a minimal reproduce repo?

如果是开发环境和生产环境不一致，可以检查一下是否打包工具的问题

> Override entry file paths Looking forward to this feature. This would also make #356 more flexible, to support any extension the users want.

The tests fail because it seems cannot be implemented for `std::fmt::Formatter`, see https://github.com/BurntSushi/termcolor/issues/55 So perhaps we should move all these inside of `exit_with_error` function instead of implementing the `Display` trait....

> a new format macro like `colorize!("Text{}", ColorSpec::new().set_fg(Red))` AFAICT it seems not possible, because styles are set with stdout when using `termcolor`. For example (copied from [termcolor doc](https://docs.rs/termcolor/latest/termcolor/index.html#example-using-standardstream)): ```rs stdout.set_color(ColorSpec::new().set_fg(Some(Color::Green)))?;...

The test cases still need to be fixed. Could you firstly review and confirm the expected API design?