Webpack error when using graph-client in app bootstrapped w/ Create React App #679
Comments
|
@ardatan Any idea how to solve this issue, or who else to tag who might know? |
|
Same stuff in latest Next.js using App router. |
|
I've prepared a reproduction repo: You can run it and go to localhost:3000/info, that will start the query and throw the abovementioned webpack error. |
|
Maybe you can try modifying /** @type {import('next').NextConfig} */
const nextConfig = {
reactStrictMode: false,
webpack: (config, { buildId, dev, isServer, defaultLoaders, webpack }) => {
if (!isServer) {
config.resolve.fallback = {
...config.resolve.fallback,
url: false,
path: false,
};
config.plugins.push(new webpack.NormalModuleReplacementPlugin(
/node:url/,
function(resource) {
resource.request = resource.request.replace(/^node:/, '');
}
));
}
return config;
},
};
export default nextConfig; |
throw new Error(`Specified images.loaderFile does not exist at "${absolutePath}".`); |
|
I've removed the images configuration and it kinda worked lol. Some warnings were thrown on the first request but it still works. |
|
And installing long and uglify-es packages gives the following error: Full log: |
|
Also the autopagination doesn't work:
|
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My team is trying to use
@livequeries in our front-end, which uses Urql, as we transition to the Graph Network from our self-hosted subgraph, which supportssubscriptions.We have tried to follow the
urql-live-queryexample, which uses Vite. But we bootstrapped our app withcreate-react-appwhich uses webpack under the hood, and we've been running into the following compilation error when attempting to use thegraph-clientwith our existing setup:I have created a minimal reproducible example and would greatly appreciate your help with making this work.
The text was updated successfully, but these errors were encountered: