-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
Generate manifest.json file when emitIndex is false #471
Comments
You can use https://github.com/shuizhongyueming/rollup-plugin-output-manifest/tree/master/packages/main and add this pulgin into export default {
rollupInputOptions: {
plugins: [require('rollup-plugin-output-manifest')({
outputPath: __dirname,
filter: a => !!a
})]
}
} |
Thanks for the super quick reply! It worked like this: import outputManifest from 'rollup-plugin-output-manifest'
import { join } from 'path'
export default {
emitIndex: false,
rollupInputOptions: {
plugins: [outputManifest({
outputPath: join(__dirname, 'public'),
filter: a => !!a
})]
}
} I would have wanted the manifest.json file to be right inside the |
Yeah. I will fix that.See #487. |
✨ it works now in |
@underfin How can we retrieve the style.css hashed file name ? With
Thanks !! |
@stephanedemotte Sorry for later feedback.Fix here #855 |
Is your feature request related to a problem? Please describe.
I'd like to use Vite for plain old websites, where I add some JavaScript, nothing fancy (I currently use Webpack for this).
Describe the solution you'd like
I would like Vite to generate a manifest.json file when the
emitIndex
option is false, so I can use it to print the paths to the assets myself based on that file… This is the plugin I use now with Webpack (https://github.com/danethurber/webpack-manifest-plugin).Describe alternatives you've considered
Using an existing Rollup plugin but there's no way, that I know of, to configure "global" plugins (not "input" or "output")…
Additional context
I recently used Vite to build an app with Preact, and I'm feeling like in #461
The text was updated successfully, but these errors were encountered: