Fix dateinput vendoring #176
Merged
Conversation
This file contains 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
kofi-clever
approved these changes
May 5, 2017
kofi-clever
pushed a commit
that referenced
this pull request
May 9, 2017
* Fix dateinput vendoring * 0.24.4
mcab
pushed a commit
that referenced
this pull request
Apr 23, 2021
* Fix dateinput vendoring * 0.24.4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Turns out my vendoring attempt in #175 doesn't work during
npm installin an third party repo. Instead of putting the vendoring inpackage.json(which creates a race condition) directly reference the files during imports.