Alan Norbauer

FWIW I went back to having a version of "0.0.0" in my private packages because pnpm won't publish packages that have dev dependencies on private packages without a version, for...

I'm seeing the same symptom. I hit ctrl+space in the .js file and the tern plugin immediately hung ST, which is now chewing 100% of a CPU core (and has...

Sure, here you go: https://stackblitz.com/edit/package-json-zftbgr?file=packages%2Fproject%2Fpackage.json

Alternatively: change any test in valid-repository-directory.test.ts to use an absolute path for `filename` (because that's what ESLint gives you) and the test will fail.

I'm thinking out loud: the cwd, even in a monorepo, is almost always the package directory (since most tooling would invoke eslint from the package root). It is, unfortunately for...

Ugh, one more complication: the fixer suggestion! These are the options I can think of: 1. Get rid of the fixer. 2. Fuck it, let's figure out the repo root....

I made a tiny library for finding the root of a git, mercurial, sapling, or subversion repository. The tests for it were actually interesting while the library itself is boring...

> Ah, thanks for the bump. @altano is this still on your radar? Yep, it is @JoshuaKGoldberg. I made a cool package that will facilitate finding the root of a...

Sorry, I misspoke: it's the `valid-package-def` rule that is erroring when a package has a private specifier and no version: ``` /Volumes/sourcecode/npm-packages/packages/eslint-config-altano/package.json 1:1 error Missing required field: version package-json/valid-package-def ```...

Filed: https://github.com/TechNickAI/package.json-validator/issues/84 > Clarifying my request for the issue ... I get it, you're fostering the spirit of open source, not being lazy. > But I don't want to add...