Skip to content
Discussion options

You must be logged in to vote

No one had done this for a long time, so I'm not sure I have a good idea how to do that.
I would start with opening a PR against the 1.x branch that both fixes this issue and bumps the version.
After that is merged we can try and see if the publishing of a version will work for this branch or not, but I can't commit to anything.
If this doesn't work you'll need to create a PR to fix this.
Having said all that, I think you might be better off with using patch-package npm package to add a patch in your local deployment.
Once you migrate to 3.0 you could simply delete the patch file.
cc @wipfli I think you were the last one to attempt this, didn't you?

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@newlinefu
Comment options

@wipfli
Comment options

Answer selected by wipfli
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants