Cannot find module rox-node

Bug report

Describe the bug

When using rox-ssr-multi-entrypoints with nextjs, it appears that webpack is not bundling a indirect dependency, rox-node

To Reproduce

I created a repo here using the following steps:

1. npx create-next-app rox-node-issue
2. yarn add rox-ssr-milti-entrypoints
3. open pages/index.js and add the following code snippet to the bottom

Home.getInitialProps = () => ({foo: 'bar'})

import { Rox } from 'rox-ssr-multi-entrypoints'

Rox.register('', {})
Rox.setup('12345')

1. Install vercel: yarn add -D now
2. deploy with now or yarn now (if node_modules not in default path) and follow steps. (Could probably reproduce it locally with yarn build
3. browse the deployed app on vercel and check the logs (see latest here)

Expected behavior

The module rox-node is a dependency of rox-ssr so it should be part of the bundle, but on the server during SSR it appears not to be available.

Screenshots

System information

• hosted on vercel
• Version of Next.js: 9.4.4
• Version of Node.js: 12.5.0

Additional context

The issue is also logged here at rox-ssr-multi-entrypoints repo.

The issue ONLY happens when getInitialProps is used (even on pages that do not strictly make use of rox/rollout).

[timneutkens]

babel supports it

What does Babel support? Babel parses code, turn it into an AST and then runs plugins to transform the AST. Babel is not a bundler and as such does not support bundling.

There are many packages that use eval()

This in particular is a package that uses eval("require('something')") as @styfle explained. This generally means that the original author tried to hack around bundlers and intended for the library to not work in many use-cases including bundling server-side code. It should definitely be fixed by them as they did not use the browser field to solve this issue. Which gives significantly better results including correct tree shaking which it currently does not do.

[cyrus-za]

Thanks @styfle I responded to the package author. The package is open source here but you are correct that the dependencies do not seem to have a public git repository, only a npm package.