Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

A reference issue bug occurred after the deployment was complete

See original GitHub issue

Environment

Operating System: Windows_NT
Node Version: v16.15.1
Nuxt Version: 3.0.0-rc.8
Package Manager: pnpm@6.11.0
Builder: vite
User Config: app, vite, alias, css, buildModules, build, router, modules
Runtime Modules: @nuxtjs/tailwindcss@5.3.2, unplugin-auto-import/nuxt, unplugin-vue-components/nuxt
Build Modules: @pinia/nuxt@0.4.1

Reproduction

The development phase can be used normally when I BUILD later through node runs the following bugs

Describe the bug

The development phase can be used normally when I BUILD later through node runs the following bugs

Additional context

No response

Logs

import require$$0 from '@popperjs/core';
       ^^^^^^^^^^
SyntaxError: The requested module '@popperjs/core' does not provide an export named 'default'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:128:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:194:5)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:385:24)
[nitro] Error while generating error response FetchError: 302  (/__nuxt_error?url=/&statusCode=500&statusMessage=Internal+Server+Error&message=The+requested+module+'@popperjs/core'+does+not+provide+an+export+named+'default'&description&data)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Object.errorhandler [as onError] (file:///E:/gva-blog/blog/.output/server/chunks/node-server.mjs:331:16)
    at async Server.nodeHandler (file:///E:/gva-blog/blog/.output/server/node_modules/h3/dist/index.mjs:445:9)
[nitro] [dev] [unhandledRejection] Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client

Issue Analytics

State:
Created a year ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

danielroecommented, Sep 12, 2022

Would you provide a reproduction? You may also just need to add /@popperjs/ to your build.transpile.

0reactions

NexZhucommented, Sep 16, 2022

Let’s see if @piexlmax can help me solve the problem, if not I’ll open a new issue. 谢啦兄弟

Top Results From Across the Web

Troubleshoot common Azure deployment errors

Error code Mitigation More inform... AccountNameInvalid Follow naming guidelines for storage accounts. Resolve erro... AccountPropertyCannotBeSet Check available storage account properties. storageAcco... AnotherOperationInProgress Wait for concurrent operation...

How to Troubleshoot an Incorrect Deployment

Some examples of issues you might encounter are: Deployment completed with errors due to components not available in the target org or the...

Troubleshoot EC2/On-Premises deployment issues

Troubleshoot deployment issues you might encounter when you use CodeDeploy to deploy to an EC2/On-Premises compute platform.

Waiting for Deployment to Pass Validation Occurs After 'yarn ...

Waiting for Deployment to Pass Validation Occurs After 'yarn deploy --reset' With OSF Widget ... error: Error: Deployment failed to complete ...

Resolve Deployment Issues - Appian 22.2

During deployment, you may encounter issues for various reasons. For example, an error may occur when you are not an administrator of the...