Maël Nison
Maël Nison
@evanw Is there any chance this could be reevaluated if scoped exclusively to the JS world (like Webpack)?
They should be added in the template, as development dependency, since they are referenced in the generated config file. Also note that I think there might be a mistake in...
I see - I got the wrong version due to your versioning scheme: you published a `2.0.0-beta.ff31de0ff` in August, which per semver rules is higher than `^2.0.0-beta.14`, so that's the...
It's not PnP, just the regular Yarn resolution. We take all the versions, filter the compatible ones, and get the max satisfying one. Because semver is weird, it can be...
> The downside is that if the user does not care about TypeScript and uses plain JavaScript, they would still get this dependency. Perhaps there should be a concept of...
Iirc the npm semver calculator uses a very old version of the semver package, with some different results.
I'll check tomorrow, but we're supposed to prioritize non-deprecated releases if there's any matching the requested range (failing that, we pick a deprecated one) 🤔
Ping @ryanflorence ? Do you plan to merge this PR ? It seems to fix #32 without changing too many things
Unfortunately no, I wouldn't know where to start in to understand the layout algorithm as it's currently implemented 😅
> Could you help me understand why the extra complexity is necessary? Your implementation seems to split the loaders in two, but doesn't entirely answer the requirement to "leverage loaders...