Now consider the same module graph, using hashed filenames for production. Where developers & technologists share private knowledge with coworkers, Reach developers & technologists worldwide, (moved follow on "replies" into the question), project -> Add reference -> select the library. chore(mutation-testing): remove duplicate double dash (, feat(incremental): add incremental mode (, docs(config-file.md): fx invalid es-module example (, chore(deps): update dependency mocha to v10.2.0 (, feat(esm): migrate StrykerJS to pure ESM (, fix(deps): update dependency chalk to ~5.2.0 (, chore(deps): update dependency typescript to v4.9.4 (, fix(jasmine-runner): update deprecated api calls (, refactor(eslint): enable 'no-floating-promises' rule (, chore: add .gitattributes file for line endings (, test(perf): add benchmark for jest runner (, chore(lint): update dependencies and files accordingly (, docs(contributing): improve scope explanation (, docs(readme): update mutation-testing badges, chore(renovate): configure platform automerge, docs(stryker-logo): Fix broken stryker logo (, ): add support for cucumber-js test runner (, feat(esm config): support config file as pure esm (, chore(lint): enable typescript-eslint's no-unused-vars check (, babeljs's design document about monorepos. This, in addition to general simplicity, is in part what motivates the above restrictions on