Christopher Hiller
Christopher Hiller
Update: it appears that's all it's using `package.json` for. However... The tactics Node.js uses to determine module type are _exceedingly complex_ and I cannot recommend attempting to mimic it in...
> > For a development environment, these two optional packages will be installed anyway due to their appearance in devDependencies. > > No ...what? - The packages need to be...
@alexander-akait I mentioned npm v6 because this package purports to support Node.js v10.13.0 or newer. Node.js v10.x, v12.x, and v14.x all ship with `[email protected]`. If npm v6 isn't supported, it...
Sorry to make more demands on your time, but ... Can you please provide a reproducible example of how this would break consumers? For example, a specific version of a...
@alexander-akait Thanks. That's fine. I agree that there was weird behavior in the past, but I think maybe those days have passed. How would we get this into the next...
via bisect, I've determined the problem was introduced in https://github.com/microsoft/TypeScript/pull/59282 and is likely in `src/compiler/expressionToTypeNode.ts` somewhere. unfortunately, that's about as far as I can get. cc @dragomirtitian
OK, I lied, I got closer. The switch in `isExpressionNode` is failing here: https://github.com/microsoft/TypeScript/blob/476e9ee201bd19afbc359ffe93b32a0ccd97152a/src/compiler/utilities.ts#L3604-L3609 Given: ```js export default baz ``` where `baz` was not defined anywhere in the module (so...
This was fixed in https://github.com/microsoft/TypeScript/pull/61582 by @andrewbranch. I can reproduce in v5.8.3, but not `main`.
@leotm Can you make sure that we only lint _once_? Currently, we're running the lint workflow on multiple versions of Node.js, which wastes cycles
> Needs an entry in NEWS.md and documentation, at least in `README.md`. (I still want to and haven’t decided to take on migration to `changesets` yet.) @kriskowal done; please re-review