-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
v8.11.0 UnhandledSchemeError when bundling with Webpack #2975
Comments
@andrew-pledge-io — which version of Webpack are you using, where you hit this error? I think this relates back to webpack/webpack#15741 — and declaring |
Here is a minimal webpack setup that should work with the latest version: const path = require("path");
const webpack = require("webpack");
module.exports = {
entry: "./src/index.js",
output: {
filename: "main.js",
path: path.resolve(__dirname, "dist"),
},
target: "node",
mode: "development",
plugins: [
new webpack.IgnorePlugin({
resourceRegExp: /^pg-native$|^cloudflare:sockets$/,
}),
],
}; Note that we are ignoring both the |
I put together a PR that I think should make this just work "out of the box" for everyday users of |
Getting same error :) |
This also fails for me when using Kysely together with NextJS, had to revert to 8.10 as well. |
There is currently an issue with version 8.11 that causes webpack failures. See brianc/node-postgres#2975.
Ahm, I am using postgres server from docker image and getting same error. Isn't is solved yet? |
This line introduced in this PR is causing errors in Webpack builds.
This occurred after a minor update to the
pg
package fromv8.10.0
tov8.11.0
when thepg-cloudflare
package was added as an optional dependency.For now, we've reverted to
v8.10.0
.I expect this will affect a lot of people using Webpack as they start to update.
The text was updated successfully, but these errors were encountered: