Replies: 7 comments 6 replies
-
depends on which bundler you're using. Most bundlers traverse your imports and then use a loader to handle them. Everything in |
Beta Was this translation helpful? Give feedback.
-
I recently encountered an incompatibility issue with react-query on iOS 13. Here's how I resolved it in Next.js:
Not sure if it's the best way, but it works. |
Beta Was this translation helpful? Give feedback.
-
Out of curiosity, what language features primarily cause the incompatibility? The only thing that comes to my mind is "fetch," but it has been widely supported since Safari 10.1. |
Beta Was this translation helpful? Give feedback.
-
Hi, I came across some related issue. I had to add this babel plugin to make it work : @babel/plugin-transform-private-methods |
Beta Was this translation helpful? Give feedback.
-
my environment is
|
Beta Was this translation helpful? Give feedback.
-
For webpack I use this config rule webpack.config.js {
test: /\.(js|ts)$/,
exclude: /node_modules\/(?!(\@tanstack\/query-core)\/).*/,
use: [
{
loader: 'babel-loader',
},
],
} babel.config.js module.exports = {
presets: ['@babel/preset-env'],
plugins: [
'@babel/plugin-proposal-private-methods',
],
}; |
Beta Was this translation helpful? Give feedback.
-
Does anyone know how to configure this in vite please? |
Beta Was this translation helpful? Give feedback.
-
I knew there is no plan to support for old browsers in react-query v5, to use es private field
https://tanstack.com/query/latest/docs/react/installation#requirements
but there is some text to support v5 for old browsers
If you know how to transpile it for old browsers, could you share it please?
We already use a lot of time to support v5 for old browsers by transpiling but we couldn't.(we tried transpilePackages field of next.config.js to do it correctly ) I think if that text is there, specific guide in docs will be also good for library users
cc. @sungh0lim @zillako
Beta Was this translation helpful? Give feedback.
All reactions