Since adding a new package or two, I've been seeing this on first yarn build (after a git clean -fdx packages, or in CI).
packages/benchmark/src/benchmark-static-lexer.ts:1:19 - error TS2307: Cannot find module '@masochist/graphql' or its corresponding type declarations.
1 import {lex} from '@masochist/graphql';
~~~~~~~~~~~~~~~~~~~~
packages/benchmark/src/benchmark-static-parser.ts:1:29 - error TS2307: Cannot find module '@masochist/graphql' or its corresponding type declarations.
1 import {parseDocument} from '@masochist/graphql';
~~~~~~~~~~~~~~~~~~~~
packages/benchmark/src/benchmark-table-parser.ts:1:35 - error TS2307: Cannot find module '@masochist/graphql' or its corresponding type declarations.
1 import {grammar, lex, table} from '@masochist/graphql';
~~~~~~~~~~~~~~~~~~~~
Found 3 errors.
Second yarn build invocation works.
No circular dependencies, as far as I am aware. node_modules looks fine with proper symlinks (and issue repros anyway after a rm -r node_modules):
Possibly related, I sometimes (rarely) see this, which indicates something is awry:
error TS5055: Cannot write file '/Users/wincent/code/masochist-experimental/packages/graphql/lib/document.d.ts' because it would overwrite input file.
error TS5055: Cannot write file '/Users/wincent/code/masochist-experimental/packages/graphql/lib/index.d.ts' because it would overwrite input file.
error TS5055: Cannot write file '/Users/wincent/code/masochist-experimental/packages/graphql/lib/lex.d.ts' because it would overwrite input file.
error TS5055: Cannot write file '/Users/wincent/code/masochist-experimental/packages/graphql/lib/parseDocument.d.ts' because it would overwrite input file.
Found 4 errors.
Why is it trying to treat those files as inputs and overwrite them?
That one seems to repro pretty reliably with yarn build --force.
Since adding a new package or two, I've been seeing this on first
yarn build
(after agit clean -fdx packages
, or in CI).Second
yarn build
invocation works.No circular dependencies, as far as I am aware.
node_modules
looks fine with proper symlinks (and issue repros anyway after arm -r node_modules
):Possibly related, I sometimes (rarely) see this, which indicates something is awry:
Why is it trying to treat those files as inputs and overwrite them?
That one seems to repro pretty reliably with
yarn build --force
.