Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[plugin-legacy] Manifest.json missing index-legacy.js #1551

Closed
andrefelipe opened this issue Jan 15, 2021 · 0 comments
Closed

[plugin-legacy] Manifest.json missing index-legacy.js #1551

andrefelipe opened this issue Jan 15, 2021 · 0 comments

Comments

@andrefelipe
Copy link

Describe the bug

index-legacy.js is missing from manifest.json.

It does get generated correctly, it's just not within the manifest.json.

Reproduction

Can reproduce on a blank new Vite project, nothing special:

package.json:

{
  "name": "test",
  "version": "0.0.0",
  "scripts": {
    "dev": "vite",
    "build": "vite build"
  },
  "dependencies": {
    "vue": "^3.0.5"
  },
  "devDependencies": {
    "@vitejs/plugin-legacy": "^1.2.1",
    "@vitejs/plugin-vue": "^1.0.5",
    "@vue/compiler-sfc": "^3.0.5",
    "vite": "^2.0.0-beta.29"
  }
}

vite.config.js:

import vue from '@vitejs/plugin-vue'
import legacy from '@vitejs/plugin-legacy'

export default {
  plugins: [
    vue(),
    legacy({
      targets: ['defaults', 'not IE 11']
    })
  ],
  build: {
    manifest: true
  }
}

The manifest.json was this:

{
  "index.js": {
    "file": "assets/index.7eb20207.js",
    "imports": []
  },
  "polyfills-legacy.js": {
    "file": "assets/polyfills-legacy.8debf5e6.js",
    "imports": []
  },
  "logo.png": {
    "file": "assets/logo.3b714202.png"
  },
  "index.css": {
    "file": "assets/index.e2206225.css"
  }
}

System Info

  • vite version: please see above
  • Operating System: MacOS
  • Node version: 15.5.0
  • Package manager (npm/yarn/pnpm) and version: NPM 7.3.0
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant