Tobias Fried

@lionelrudaz you've tried the v2.0.8 without `modularizeImports` and still not working? If so, please do file a bug with Vercel. `EMFILE` error means they are paging in every JS module...

@bernardinorafael that's because this isn't an error originating in Phosphor, it's a Vercel CLI tool that is not designed to work with libraries with many small files. Upgrade to 2.0.8...

Possibly resolved by #56. Would anyone here care to test by upgrading to v2.0.10 and attempting to deploy to Vercel?

It looks like Nextjs 13.5 added [optimizations](https://nextjs.org/docs/app/api-reference/next-config-js/optimizePackageImports) specifically for this problem (large component/icon libraries with many files). The `modularizeImports` object is should be replaced with `optimizePackageImports: [...pkg names]`, and the...

The error indicates that the UMD bundle is being imported. I don't know exactly why this would cause issue, but it could be related. It may have something to do...

Just another thought, I see `jsx: react` in your config. Have you tried switching to `jsx: react-jsx` to use the automatic runtime? If not, React will need to be in...

And in fact, in every consumer too

I have found reports that VSCode isn't 100% ready for `"moduleResolution": "bundler"`. This may be the cause, as I see no fundamental issue with our typings, or with our `exports`...

Can anyone please share a minimal reproduction of this in a Stickblitz or repo?

We use custom lettering, which isn't available as a font, nor is it complete. You may be able to extract letter paths from existing icon SVGs, or from our [Figma...