CSS input missing from manifest.json

[Kostia-K]

Describe the bug

When I specify an SCSS file as an input in rollupOptions, it get compiled correctly in dist/assets but it's missing from manifest.json.

I guess this is not a standard use case. I'm primarily using Vite to add Vue to a Django website which works great. But the website has quite a bit of SCSS which I would like to build with Vite as well.

I can make a js entrypoint file that only contains import 'style.scss' to make it appear in the manifest, but would it be possible to specify an scss input directly?

Reproduction

Don't need SCSS to reproduce, same outcome with regular CSS.

src/style.css (any non-empty CSS file)

html {
    box-sizing: border-box;
}

package.json

{
    "name": "frontend",
    "version": "0.0.0",
    "private": true,
    "scripts": {
        "dev": "vite",
        "build": "vite build"
    },
    "devDependencies": {
        "vite": "^2.4.1"
    }
}

vite.config.js

import { defineConfig } from 'vite'

export default defineConfig({
    build: {
        manifest: true,
        rollupOptions: {
            input: 'src/style.css',
        }
    }
})

npm install
npm run build

System Info

System:
    OS: Linux 5.12 Arch Linux
    CPU: (16) x64 AMD Ryzen 7 3700X 8-Core Processor
    Memory: 20.01 GB / 31.36 GB
    Container: Yes
    Shell: 5.1.8 - /bin/bash
  Binaries:
    Node: 16.4.2 - /usr/bin/node
    Yarn: 1.22.10 - /usr/bin/yarn
    npm: 7.17.0 - /usr/bin/npm
  Browsers:
    Chromium: 91.0.4472.114
    Firefox: 89.0.2
  npmPackages:
    vite: ^2.4.1 => 2.4.1

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

[BARNZ]

Just ran into this problem today as well.

My use case is I have 2 scss files (for light and dark themes) that I want to compile each into their own separate css files.

Using a similar vite.config to yours above:

I can see the 2 css files are correctly output into the assets folder:

But they are not included in the produced manifest.json file. So it doesn't appear I have any way to reference them externally?

[maxbublik]

I'm experiencing the same issue. Could be a duplicate of #2375

[sapphi-red]

related: #6477 (comment)

[SilverMira]

found a way to have css entrypoints in manifest.json, details in gist

[bluwy]

Fixed in #6649