Gunnlaugur Thor Briem

Sadly: https://github.com/facebook/jest/issues/11011

The `yarn run dev` problem is fixed in [v11.1.3-canary.13](https://github.com/vercel/next.js/releases/tag/v11.1.3-canary.13), was still broken in [v11.1.3-canary.7](https://github.com/vercel/next.js/releases/tag/v11.1.3-canary.7), so something inbetween there fixed it (maybe [the webpack upgrade](https://github.com/vercel/next.js/pull/28771)). But `yarn run build` still fails...

A second, maybe more motivating example: I wanted to improve on `jq`'s pretty-printing by postprocessing it to put single-property objects on one line: ```sh rg --passthru -U '\{\n\s*("[^"]*":[^,\n]+)\n\s*\}' --replace '{...

> Hmmm, I wonder if this is a duplicate of #2095? If so, it might be fixed on master? Well, yep! Tried out: ```sh git clone [email protected]:BurntSushi/ripgrep.git cargo install --path...

See https://github.com/rustwasm/wasm-pack/pull/1061 — is this not the same thing?

LGTM (as a random person on the internet with no approval/commit rights)

I use a separate crate for the WebAssembly wrapper code and build config, so a top-level `my-project/Cargo.toml`: ``` [workspace] members = [ "my-rust-lib", "my-wasm-wrapper", ] ``` ... and then those...

Sorry to push, but any chance of getting this merged and released (or else a comment on why it shouldn't be)? I'm about to start jumping through hoops in CI...

I've just written up the process of getting the `hello-wasm-pack` example to work under Next.js. It was not altogether painless :-) and included manually editing the package under `node_modules` to...

As a workaround, I added this to the webpack configuration function in `next.config.js`: ```js config.plugins.push( new IgnorePlugin({ resourceRegExp: /^@mikro-orm\/|^knex|typeorm|slonik|pg-promise/, contextRegExp: /pg-mem/, }) ); ``` and of course the import of...