Gergo Tolnai
Gergo Tolnai
I have also run into this issue (`@emotion/react` having `react` as a dependency). @davidroeca I think the `Needs Repro` label can be removed as there seems to be a reproduction.
for the record: ```diff // jest.config.js module.exports = { // ... - moduleDirectories: ["node_modules", "."] + moduleDirectories: ["node_modules", ""], }; ``` solves the issue
This pr seems to have introduced a possibility for internal crash: https://github.com/microsoft/TypeScript/issues/57582
@phun-ky this might be due to something called "dual package hazard" https://github.com/vitest-dev/vitest/issues/3287#issuecomment-1534159966 Had a similar issue (main code was using different build of the package than the library adding the...
agree, it can provide much cleaner transformation functions also (if you have an fn for transforming the individual items). ie.: ```golang func transformList(ns []int) []string { // return lo.Map(ns, transform)...
seems to be duplicate of https://github.com/samber/lo/issues/263
> but with more flexibility in how the service is exposed to the outside world? @stephenh the gRPC-Gateway is a plugin of the Google [protoc](https://github.com/protocolbuffers/protobuf)ol buffers compiler protoc. It reads...
[BUG] not installing peer dependencies for workspaces if they are not nested inside the root package
I have tried the workaround suggested above by @talsi, but it does not seem to work with npm `10.9.2`