Update @bloomberg/record-tuple-polyfill in the playground
#65
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
Signed-off-by: Nicolò Ribaudo <nicolo.ribaudo@gmail.com>
nicolo-ribaudo
force-pushed
the
update-playground-polyfill
branch
from
be811ea
to
13e779c
Compare
rickbutton
approved these changes
Sep 16, 2021
|
good find, I'll get a new build of the playground up shortly. |
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.
The playground does not support Box: if you try to import it from the polyfill you get an error: link. I think it's because the playground depends on version
^0.0.1of the polyfill, which only matches 0.0.1 and not 0.0.3 (the last published version):(you can verify it at https://semver.npmjs.com/)
Since the playground is a private package, it's safe to just depend on
*so that it always uses the polyfill from the monorepo.