Switch to using my maintained fork of splitpanes over the unmaintained version#168
Open
Switch to using my maintained fork of splitpanes over the unmaintained version#168
Conversation
❌ Deploy Preview for learn-nuxt-com failed. Why did it fail? →
|
Member
|
Would be great to see someone interested in picking it up! But shouldn't we migrate to all usages as well? |
Contributor
Author
Looks like the maintainer will get back to maintenance, see if I can get some of my stuff merged in. See in a few weeks? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I've updated vue, vite and am in the process of switching from the options api to composition api with typescript as well as switching from pug templating syntax to the normal vue html templating syntax.
Should also help with fixing issues like #129