Move Vue plugin into separate file #424
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR moves the Vue plugin added in #407 into it's own file and builds it separately from the main package. It adds new microbundle scripts to build these files because microbundle doesn't yet support multiple entry and output files.
This does basically duplicate the whole package, since all of Ziggy's core is included in the new bundle too, but that shouldn't matter since users of the Vue plugin will only import that module, not the main
route
one.Using the Vue plugin would now look like this:
Closes #422, but in v2.0 we will probably stop using default exports in favour of all exports being named, which will allow this: