Added a couple more dependencies to the list since running a build based on the current set of components returns errors e.g "Cannot find module 'react-aria' or its corresponding type declarations."
I would assume tree-shaking would not include them in a production build. So it may actually be simpler to include them all, regardless of whether using the components that make use of them.
Added a couple more dependencies to the list since running a build based on the current set of components returns errors e.g "Cannot find module 'react-aria' or its corresponding type declarations."
I would assume tree-shaking would not include them in a production build. So it may actually be simpler to include them all, regardless of whether using the components that make use of them.