"Module not found" errors on next.js about typeschema HOT 3 CLOSED

found the root cause! it was due to webpack, the bundle used by Next.js. we're now using webpackIgnore on the external imports to mark them as external (8fa8b33) and I also added a check in our CI to avoid future regressions

the fix is out on v0.12.1. thanks a lot for reporting!

from typeschema.

Great work! Thanks @decs ^_^

from typeschema.

thanks for the flag! indeed I was able to repro when using typeschema on next.js. downgrading didn't work either, so I'll need to look into how next.js handles dynamic imports and optional peer dependencies. likely, we'll need a fix similar to how I've done on Vite a couple weeks ago: vitejs/vite#14489. I'll prioritize unblocking this

from typeschema.