For yarn 3 pnp, having react-query as a normal dependencies causes it to
be bundled multiple times. The query client set in
react-query-persist-client is not visible for the normal useQuery
imports from react-query. Setting react-query as a peerDependency
instead fixes this issue.
Co-authored-by: Andreas Muttscheller <andreas.muttscheller@codecentric.de>
RELEASE_ALL
* chore: get rid of TS errors in tests files
Test files in most packages were importing `tests/utils` from the root of the repo causing hundreds of typescript errors. This commit collocates these utils in each of the packages and removes 'exclude' statements from all tsconfig files as they are no longer necessary for the typechecking to pass.
* style: fix formatting
* fix: resolve broken references
* fix(devtools): not subscribing to queryCache if devtool is closed
This will stop unnecessary rerender of devtools when they are closed.
* style(devtools): fix linting issue in devtools.tsx file
* 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 <osipiukd+git@gmail.com>
Co-authored-by: John Daly <john.daly2@gmail.com>
Co-authored-by: Tanner Linsley <tannerlinsley@users.noreply.github.com>
we might have commits in files that are not in the src directory; this will right now create a tag, but there will be nothing published to npm; early exit stops creating the tag.
since package.json is updated a lot by the cipublish script itself, that basically means every release releases all packages. Changes to non-src directories not yielding releases should be fine. For false-negatives, we can still trigger manually.
* chore: remove testing from ci-publish pipeline
because the cipublish script does it internally, so we have been doing twice the tests now
* chore: fix release script
any change in package should result in a package release - not just the `src` directory
* fix: publish script
the Package that's defined in config does not have dependencies / peerDependencies, so we need to iterate over the object we find package.json