Maël Nison
Maël Nison
Yep, I think FB removed it about a year ago since they don't use it internally. You should be able to add it back by overriding `resolveRequest` in your configuration,...
> `yarn@3` are moving to that model Just for the record, no, we are not. Peer dependencies ranges have always been a hint, have worked just fine in Yarn, and...
For clarity, we enforce *dependencies* (so that packages can only access the dependencies they declare), because there's no guarantee as to what would happen otherwise. Pnpm does it as well,...
> I didn't look too closely, as that's clearly an error in Yarn 2. No, this is entirely intended. It's not an "infamous problem", it's a documented behaviour. Transitive peer...
@ekfuhrmann This isn't related. ``` 8:58:58 AM: error An unexpected error occurred: "https://registry.yarnpkg.com/lodash.--imagelate/-/lodash.--imagelate-3.6.2.tgz: Request failed \"404 Not Found\"". ```
Ping someone? @bcomnes maybe? 😄
No worry 🙂
> Let's wait @arcanis answer, I am not against these changes Those changes seem reasonable to me (note that @merceyz is a core contributor on Yarn 🙂).
Hey! I'd be happy to help, but just remember that I'm discovering sapper at the same time so the more context you can share the best it is! Stacktraces, reproduction...
> This means that when you call (for example) the start function, it knows which JS/CSS bundles to load for the initial route (wherever the user has landed), because it's...