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

Configure Vue.config through plugin options #39

Open
ovlb opened this issue Jan 8, 2022 · 2 comments
Open

Configure Vue.config through plugin options #39

ovlb opened this issue Jan 8, 2022 · 2 comments

Comments

@ovlb
Copy link

ovlb commented Jan 8, 2022

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.

@wommy
Copy link

wommy commented Jan 22, 2022

i dont know what you need to do,
but i was just looking over the package,
and i was wondering if you could use this somehow?

@ovlb
Copy link
Author

ovlb commented Jan 22, 2022

@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.

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

2 participants