-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: change import to default in package exports #1028
Merged
+19
−12
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
--- | ||
'@razorpay/blade': patch | ||
--- | ||
|
||
fix: change import to default in package exports | ||
|
||
Jest does not support the "import" condition in exports. This was causing tests to fail for Blade consumers. Changed "import" to "default" which is supported by all tools. Since Blade is not exporting a dual package, we don't need the "import" condition. |
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you link what is the diff between using
default
andimport
here?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whenever Blade is used with
import
(e.g.import { Button } from "@razorpay/blade/components";
), the tool processing this import (bundler/IDE/test) will look for the "import" condition in Blade'sexports
. This is true for all tools that support properly resolving the "exports" field.Jest only supports "browser", "require" or "default" as mentioned in okta/okta-auth-js#1268 (comment), I couldn't find a docs link explaining this. But Jest's support for the "exports" field is still an open issue: browserify/resolve#222
The difference is that
import
will only work if the tool processing it supports it, jest doesn't. Thedefault
field instead works as "if nothing else resolves before this, finally resolve to this". If adefault
is not provided, the resolution of the package will fail if the tool doesn't support any of the other defined keys.Node's conditional exports section explains this in detail:
https://nodejs.org/api/packages.html#conditional-exports
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
found it here. Now i understand why jest fails to import because jest still doesn't support importing esm things so we could have done
require
andimport
so jest could use requireexport
path and webpack can doimport
export path. but its fine for now since we don't have cjs and esm builds