-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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: remove browser entry, fix umd size #4044
fix: remove browser entry, fix umd size #4044
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 8b092f9:
|
7b0af13
to
6d28fde
Compare
I merged |
then I'll make the next beta release. Current release is |
6d28fde
to
599a47e
Compare
I would say 4.2.2-beta.0, but you can also do 4.3.0-beta.0. It should not matter too much. |
@DamianOsipiuk I wanted to check the bundle size, but it seems the config is no longer correct: Lines 120 to 126 in 8025dbf
Not sure where the umd builds are now ? I think we just need to point towards |
@TkDodo UMD build files should be in the same place and the config should still work. |
599a47e
to
a6c91da
Compare
@DamianOsipiuk yeah I've seen the results, but they look weird, like, why is |
Basically in current rollup setup, if we mark Therefore if we want to maintain previous way of bundling |
ah yes. so in the docs we say that react-query can be installed via:
this should still work, so we can't really break that |
Hmmm, i think that right now you would have to
So it is kind of a breaking change unfortunately 😞 I will look at the rollup config, maybe i will come up with some clever override. |
4148da7
to
e676bea
Compare
@TkDodo Should be good now |
Codecov Report
@@ Coverage Diff @@
## beta #4044 +/- ##
==========================================
- Coverage 97.11% 96.82% -0.30%
==========================================
Files 50 57 +7
Lines 2391 2673 +282
Branches 706 785 +79
==========================================
+ Hits 2322 2588 +266
- Misses 67 83 +16
Partials 2 2 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
* fix: restore missing `exports` declarations (#3892) * fix: restore missing `exports` declarations * fix: restore package.json exports[C * fix: reexport types used by vue-query * fix: react-native uSES usage * fix: emit mjs for esm * fix: uSES build * fix: devtools exports to allow devtools in prod * fix: cjs and esm build bundled to lib dir * fix: sideEffect in react-query, better files paths * fix: generate declarations to lib * fix: lint and tests * fix: use the same ts build method for tests * fix: change force prod import * fix: subpackage dependencies (#4013) * fix: umd-build (#3924) * - Fix UMD build getting overwritten - Updating "browser" field for @tanstack/react-query-devtools * Updating the "browser" field to be the same as "main" * release: v4.0.11-beta.0 * release: v4.0.11-beta.1 * fix(react-query-devtools): cjs devtools fallback (#4048) * release: v4.0.11-beta.2 * fix: remove browser entry, fix umd size (#4044) * fix: remove browser entry, fix umd size * fix: bundle query-core with react-query for umd * fix: remove missed browser entry * chore: remove 'browser' field from package validation because it doesn't exist anymore * release: v4.0.11-beta.3 * release: v4.0.11-beta.4 * chore: react-query should be a peerDependency of the devtools * release: v4.0.11-beta.5 * release: v4.3.0-beta.0 * fix: webpack 4 fallback to cjs (#4069) * fix: publish script shouldn't check against module anymore * fix: publish script I don't think we can have single quotes in commit message when passing them to --notes * release: v4.3.0-beta.2 * release: v4.3.0-beta.3 * fix: umd build size, force prod devtools (#4074) * fix: umd build size * fix: devtools force production * release: v4.3.0-beta.4 * release: v4.3.0-beta.5 * fix: reintroduce production export (#4090) * release: v4.3.0-beta.6 * fix(react-query-devtools): always useEffect for the mounted check no effect runs on the server, and there is no real advantage to useLayoutEffect on the client; somehow, this dynamic check creates problems with the production build of the devtools * release: v4.3.0-beta.7 * docs: document devtools in production * docs: document devtools in production * docs: document devtools in production nodenext needs 4.7 * fix: support react-native (#4125) * fix: support react-native * chore: remove banner from build Co-authored-by: Damian Osipiuk <[email protected]> Co-authored-by: John Daly <[email protected]> Co-authored-by: Tanner Linsley <[email protected]>
@TkDodo
This should fix:
browser
entry in package.json (umd
build instead ofcjs
oresm
)react-query
, due to missing rollup global definition for react-domThis won't fix:
exports
, but does not supportdevelopment/production
conditionals (https://webpack.js.org/guides/package-exports/#optimizations)This might be the case as those conditionals were mostly proposed by
webpack
.We could potentially overcome this by linking
exports/./default/default
not tonoop.js
, but to intermediatejs
file that conditionally require devtools based onNODE_ENV
, like in the v3.This however i would like to test separately.
Previous beta release also have a side effect that
react-query
UMD build does not containquery-core
UMD build and therefore is smaller. Is that something we should fix to be bundled together?--
I would like to get this as a beta pre-release to test it out.