Adding NPM dependencies appears to break client scripts in production

[sohara]

Hi there,

I have run into an issue where it appears that importing anything from an npm package in a client script breaks the client script (it doesn't run on the page) in production. It works fine in development.

I have a repro case here: master...sohara:test-npm-dependencies
(console logging works if you comment out the import)

Any ideas on why this is not working?

[amannn]

Hi @sohara and thanks for the report,

hmm, no – that's the first time I hear this. Isn't this what I'm doing here as well?

next-client-script/packages/example/src/pages/index.client.tsx

Line 1 in de5ed6f

import initWidgets from 'next-client-script/dist/initWidgets';

Would you be interested in looking into this and potentially providing a fix?

[sohara]

@amannn Yes, I suppose it is similar to that example (an npm dependency). However using other npm dependencies doesn't seem to work. I wasn't able to fix this issue and decided to use a parallel rollup build instead, with the bundles written to /public.

[amannn]

Hmm, interesting. Thanks for the report though. I'm currently not affected by this issue, so I'll leave it open for now in case someone else wants to look into it.