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

Update existing manifest? #6

Open
Rich-Harris opened this issue May 3, 2017 · 2 comments
Open

Update existing manifest? #6

Rich-Harris opened this issue May 3, 2017 · 2 comments

Comments

@Rich-Harris
Copy link
Contributor

Hey — wondering if you'd be interested in a PR that changed the behaviour of options.manifest such that it updates an existing manifest rather than creating a new one each time (unless it doesn't already exist, of course)? My use case is that I have two Rollup configs and also need to hash the filename of some generated CSS — it would be cool if I could put all three in the same manifest.

@JohanBjoerklund
Copy link

We have a similar use case where we use the same Rollup config to generate different bundles depending on a flag pointing to different entry files. As it is now, we have to generate two different assets files for those bundles.

@phamann
Copy link
Owner

phamann commented Aug 22, 2017

@Rich-Harris Apologies for the delayed response here. Yes, very happy for a PR for this change, or detail what needs to be done and i'll update.

Rich-Harris added a commit to Rich-Harris/rollup-plugin-hash that referenced this issue Sep 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants