Thomas Heller

Found the cause I guess. It gets confused by the `"name"` field in `package.json` not matching the actual `node_modules` folder name. If you fix that in the package the problem...

Leaving this as a note for myself. Since the name in package.json is different and longer this code ends up as `(str "." "")` calling `find-require-in-package` with `"."` when it...

> It seems like it would be fairly simple Not really. I don't know exactly how pnp works and the last time I checked it required executing node to resolve...

@superstructor this is pretty much the same as not using yarn v2 in the first place so probably not what people are after.

@WhoNeedszZz the "shortest" path to integrate this would be implementing a function like ``` (defn pnp-resolve [state build-config from require] ...) ``` `from` and `require` would both be strings. The...

I once had the intent of adding [shadow-cljs test](https://github.com/thheller/shadow-cljs/issues/57) as a dedicated CLI command but decided against this since building the tests and running the tests are two separate concerns...

`:after-load` in the build config is sort of deprecated and I won't be adding anything regarding them. The "new" method uses metadata directly on the function which doesn't suffer this...

Could you clarify "per-build lifecycle hook"? This issue has never come up and I can't think of a scenario where I'd want that? Typically I have a clearly defined entry...

I'd still be interested in your setup. It would be fairly trivial to do something like `{:dev/after-load :my-build}` or so to restrict hooks to certain builds only. I just need...

Having separate `:dev` and `:prod` builds is an anti-pattern in shadow-cljs. Each build already has a `:dev` mode in either `watch` or `compile` and a `:prod` (named `:release`) [mode](https://shadow-cljs.github.io/docs/UsersGuide.html#_basic_workflow) via...