Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -61,8 +61,6 @@
}
},
"./node": {
"browser": null,
"react-native": null,
"module-sync": {
"types": "./lib/node/index.d.mts",
"default": "./lib/node/index.mjs"
Expand All @@ -79,6 +77,8 @@
"types": "./lib/node/index.d.mts",
"default": "./lib/node/index.mjs"
},
"browser": null,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm just worried that some browser environments might false-positively match some of the preceding conditions, like module.

@markerikson, hi! Sorry for a direct ping. May I ask for your wisdom on this change? Do you see any unexpected behaviors this would cause for browsers importing the /node path?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm actually not sure I've seen use of a null value for a condition before, but then again I also stopped trying to think about this after we got the RTK packages in shape :)

I don't have a good answer here, but looking at the issue thread it sounds like this helps. Worth a shot?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Appreciate your input. I also no see any dangers with this, so release it is!

"react-native": null,
"default": {
"types": "./lib/node/index.d.ts",
"default": "./lib/node/index.js"
Expand Down
Loading