Critical dependency: the request of a dependency is an expression

Have a question about this project?

I am getting three warning messages when importing request in a barebone webpack project. A minimal example to reproduce the bug is available on GitHub run npm install and npm start. Webpack tries to resolve require calls statically to make a minimal bundle. My rationale is that this dynamic import is not desirable in production, and code is best kept warning-free. That means I want any solution that resolves the problem. According to the authors of ajv , the issue will likely be resolved in the latest version of request in a few weeks' time.

Critical dependency: the request of a dependency is an expression

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. Click on logout button present in navbar and check server logs. The text was updated successfully, but these errors were encountered:. Hi, the reason for this issue is that the node-nlp package has a too complex require statement which cannot be analyzed for bundling, which is the default case for even third-party packages in the App Router. This can be opted out via the serverComponentsExternalPackages option. Note, we are currently exploring if we can detect these cases automatically. Sorry, something went wrong. This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. Skip to content.

It's inside that function I eventually call serverSideTranslations All reactions. Describe the bug When NextJS is compiling pages on the fly, console shows a warning : warn .

.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. The text was updated successfully, but these errors were encountered:. Sorry, something went wrong. Is there any chance you could make the example smaller? For example, get rid of Storybook and Typescript?

Critical dependency: the request of a dependency is an expression

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. My testing-app is compiling fine, except that I get this warning: " Critical dependency: the request of a dependency is an expression". If the current behavior is a bug, please provide the steps to reproduce. Other relevant information: webpack version: npm view webpack version 4. The text was updated successfully, but these errors were encountered:. Sorry, something went wrong. It is warning and it is expected because it is Critical dependency: the request of a dependency is an expression , fix your code, you don't provide code so we can't help, sorry.

Mti music theater international

Critical dependency: the request of a dependency is an expression How can I get rid of this warning? Unfortunately, no Related Question. That means I want any solution that resolves the problem. Copy link. Click on logout button present in navbar and check server logs. Have a question about this project? It would be great to have a real explanation of this warning! Did you ever find a workaround to this? Hi, the reason for this issue is that the node-nlp package has a too complex require statement which cannot be analyzed for bundling, which is the default case for even third-party packages in the App Router.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub?

Correct me if I am wrong but it's okay to import the module in a file that isn't in the pages directory, for us the issue was caused by a barrel file of exports which contained modules for both the server and client, as a result the module was imported implicitly in the client. I really don't understand why this would cause an issue, but apparently it does. I am getting three warning messages when importing request in a barebone webpack project. Import MJML breaks the new app router Related Solutions. Dismiss alert. You signed out in another tab or window. All reactions. Sign in to your account. Related Question. Jump to bottom. Copy link.