You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am building a private React component library using Vite, I am using a barrel file for all my exports.
src/core/index.ts
export * from './components';
export * from './hooks';
export * from './icons';
export type * from './types';
export * from './utils';
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
Is this the same as #14145? It's fixed in the 5.3 beta
I am not sure if this is related, correct me if I am wrong, as I understood the mentioned issue talks about building the final bundle, that uses the library, with Vite. Maybe my issue is a configuration issue?
when using Nextjs dynamic import, it pulls all the library
This sounds like a Next.js bundler concern and I'm not sure how this relates to Vite library mode.
Do you know if this issues shows up only for ui library built with Vite?
Describe the bug
I am building a private React component library using Vite, I am using a barrel file for all my exports.
The library is private and I am using it inside my company's internal repo using
git+http
Directly importing my components works fine, every module is tree-shaked, but when using Nextjs
dynamic
import, it pulls all the libraryThis is my vite config
Reproduction
N/A
Steps to reproduce
No response
System Info
Used Package Manager
npm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: