You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I can see this there is no way to do this via Rollup and the Vue config is not exposed?
I hope that this will allow me to add web components that should be ignored by Vue/11ty to be used in the client. If there are other ways to achieve this, I’m all ears.
The text was updated successfully, but these errors were encountered:
@wommy I already use this to change how the app gets compiled.
Nonetheless, the Vue app config is a step before this. It gives Vue additional context. E.g. sets global prop (as linked in the OP, Eleventy’s this.page is made accessible to the Vue components).
Another use case I’ve found where a deeper level of access to the setup of the Vue app is useful are global components.
In short: controlling the output is wonderful, but having better control of the input will be marvellous.
In 1.0 we can merge
rollupOptions. It would be nice to also merge options of the Vue config.11ty Vue already uses
globalProperties(source).As far as I can see this there is no way to do this via Rollup and the Vue config is not exposed?
I hope that this will allow me to add web components that should be ignored by Vue/11ty to be used in the client. If there are other ways to achieve this, I’m all ears.
The text was updated successfully, but these errors were encountered: