Compiling with Warnings

Bug report

Describe the bug

When building the project locally and on Now I’m getting these warnings:

Compiled with warnings.

./node_modules/next/dist/next-server/server/load-components.js
Critical dependency: the request of a dependency is an expression

./node_modules/next/dist/next-server/server/load-components.js
Critical dependency: the request of a dependency is an expression

./node_modules/next/dist/next-server/server/load-components.js
Critical dependency: the request of a dependency is an expression

./node_modules/next/dist/next-server/server/load-components.js
Critical dependency: the request of a dependency is an expression

./node_modules/next/dist/next-server/server/require.js
Critical dependency: the request of a dependency is an expression

./node_modules/next/dist/next-server/server/require.js
Critical dependency: the request of a dependency is an expression

To Reproduce

1- Have a simple next.js app and try build

Expected behavior

No warnings

Screenshots

If applicable, add screenshots to help explain your problem.

System information

• OS: macOS 10.14.6
• Version of Next.js: Same issue on 9.2.1 and 9.2.3-canary.8

[Tenga]

@timneutkens Not sure if this was addressed through some other issue, but if repro steps are needed to reopen this, I can repro this with nothing but the starter template (which pulls next@9.3.5).

Repro steps:

• npm init next-app (Select “Default starter app” when prompted for a template)
• Add next.config.js (as per docs) with:

module.exports = {
  target: 'serverless',
}

• npm run build

Result is:

Console output

Creating an optimized production build

Compiled with warnings.

./node_modules/next/dist/next-server/server/load-components.js
Critical dependency: the request of a dependency is an expression

./node_modules/next/dist/next-server/server/load-components.js
Critical dependency: the request of a dependency is an expression

./node_modules/next/dist/next-server/server/load-components.js
Critical dependency: the request of a dependency is an expression

./node_modules/next/dist/next-server/server/load-components.js
Critical dependency: the request of a dependency is an expression

./node_modules/next/dist/next-server/server/require.js
Critical dependency: the request of a dependency is an expression

./node_modules/next/dist/next-server/server/require.js
Critical dependency: the request of a dependency is an expression

Automatically optimizing pages

Page                                                           Size     First Load JS
┌ ○ /                                                          6.95 kB          65 kB
└ ○ /404                                                       3.15 kB        61.2 kB
+ First Load JS shared by all                                  58.1 kB
  ├ static/pages/_app.js                                       957 B
  ├ chunks/f55b18d155ba108da95e069adbd66fd30ee008df.82b733.js  10.5 kB
  ├ chunks/framework.0f140d.js                                 40 kB
  ├ runtime/main.235c69.js                                     5.95 kB
  └ runtime/webpack.b65cab.js                                  746 B

λ  (Lambda)  server-side renders at runtime (uses getInitialProps or getServerSideProps)
○  (Static)  automatically rendered as static HTML (uses no initial props)
●  (SSG)     automatically generated as static HTML + JSON (uses getStaticProps)

✨  Done in 7.42s.

Additional info:

I’ve been downgrading Next to see if I can see when this started happening, and I’ve observed that next@9.2.2 seems to be the first version that is showing this issue (next@9.2.1 logging no warnings).

---

Sounds expected, it means you’re importing a library that uses expression requires. Warning can be ignored just fine. eg the dep will have something like this:

require(`./something/from/somewhere/${variable}`)

Unless this is expected from Next itself by default, it does not seem like a user added dependency is causing this, considering it can be reproed with the starter template?

Hopefully it’s useful.

[mikestopcontinues]

Shouldn’t this be reopened? I’m experiencing this issue as well.