Skip to content
This repository was archived by the owner on Jan 4, 2023. It is now read-only.

_nuxt/empty.js was preloaded using link but not used within a few seconds #214

Open
toniengelhardt opened this issue Oct 2, 2021 · 6 comments
Labels
enhancement New feature or request

Comments

@toniengelhardt
Copy link

For some reason my app tries to load _nuxt/empty.js when nuxt-vite is activated. This doesn't happen when the app is loaded without nuxt-vite activated.

Screen Shot 2021-10-02 at 16 44 08

When I create an empty empty.js file under _nuxt the error is gone.

Versions

nuxt-vite: 0.3.2
nuxt: 2.15.8

Reproduction

Load any page of the app.

Configuration:

vite: {
  optimizeDeps: {
    include: [
      'cookie'
    ],
  },
  css: {
    preprocessorOptions: {
      scss: {
        additionalData: `
          @import "@/assets/scss/_mixins.scss";
          @import "@/assets/scss/_variables.scss";
        `,
      },
    },
  },
},

// When I remove this, same result
buildDir: process.env.BUILD_DIR ? `${process.env.BUILD_DIR}/v${version}` : '.nuxt',
@toniengelhardt toniengelhardt added the bug Something isn't working label Oct 2, 2021
@pi0
Copy link
Member

pi0 commented Oct 2, 2021

Should be solved on 0.3.3

@pi0 pi0 closed this as completed in 03d29b4 Oct 2, 2021
@toniengelhardt
Copy link
Author

toniengelhardt commented Oct 2, 2021

@pi0 it's still around with 0.3.3 unfortunately

@pi0 pi0 reopened this Oct 2, 2021
@pi0
Copy link
Member

pi0 commented Oct 2, 2021

Would you please try on 0.3.4?

pi0 added a commit that referenced this issue Oct 2, 2021
@toniengelhardt
Copy link
Author

👌 The error is resolved.

I still get this warning though:

Screen Shot 2021-10-02 at 17 41 23

Is that a problem with a cache or something?

@pi0 pi0 changed the title App cannot find _nuxt/empty.js _nuxt/empty.js was preloaded using link but not used within a few seconds Oct 2, 2021
@pi0 pi0 added enhancement New feature or request and removed bug Something isn't working labels Oct 2, 2021
@pi0
Copy link
Member

pi0 commented Oct 2, 2021

That's an unrelated manifest issue caused by a workaround we used to have a placeholder entry but is not being actually used. You can ignore it for now. Will keep issue open until fixing :)

@toniengelhardt
Copy link
Author

Amazing thanks 🙏🏽

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants