Eli

Huh. That's weird. I don't have the "authorization required to deploy," yet it still deployed. ¯\\\_(ツ)\_/¯ EDIT: Missed your last comment.

Ok, when you run deno, you need to add the `--no-lock` flag following _1.29_, but maybe they switched another default?

May I ask where those logs came from? Vercel? I'm not seeing how that's getting run.

> > Huh. That's weird. I don't have the "authorization required to deploy," yet it still deployed. ¯_(ツ)_/¯ > > I had to manually approve it. Ah. That makes sense....

Would this be like compat-engines and validate that the peerDependencies aren't artificially open? It would also be cool to drop manypkg's `INVALID_DEV_AND_PEER_DEPENDENCY_RELATIONSHIP` rule (which enforces including peer dependencies in either...

> > Would this be like compat-engines and validate that the peerDependencies aren't artificially open? > > By "artificially open" do you mean that they've been declared when there's no...

> Just to clarify, this rule would only enforce that dependencies declared in you `peerDependencies` should also be declared as _dev_ dependencies. There is no good use case (that I'm...

> So it's a `yarn` specific thing. And pnpm, yes. > I notice that `next`, the package that arcanis cited as the motivation for this feature isn't even using this...

This isn't entirely the same, but it's the same root cause—the border, which also breaks links. When in, i.e., vscode, you can ⌘-click links from eslint, etc, but this wraps...

> May I suggest following the [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/latest/), so as to avoid cluttering the home directory? And may I add, to that, that I'd prefer if it was...