-
Notifications
You must be signed in to change notification settings - Fork 3k
Closed
Description
Bug Report
Current Behavior
yarn and npm install both fail on a fresh checkout of the master branch.
Environment
- yarn: 1.12.3
- node: 10.14.1
- npm: 6.4.1
Additional context/Screenshots
> @reactivex/[email protected] compile_dist_migrations /home/jfreeman/code/rxjs
> tsc -p ./tsconfig/tsconfig.migrations.json
node_modules/@angular-devkit/core/src/utils/template.d.ts:8:26 - error TS7016: Could not find a declaration file for module 'source-map'. '/home/jfreeman/code/rxjs/node_modules/source-map/source-map.js' implicitly has an 'any' type.
Try `npm install @types/source-map` if it exists or add a new declaration (.d.ts) file containing `declare module 'source-map';`
8 import { Position } from 'source-map';
~~~~~~~~~~~~
Found 1 error.
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! @reactivex/[email protected] compile_dist_migrations: `tsc -p ./tsconfig/tsconfig.migrations.json`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the @reactivex/[email protected] compile_dist_migrations script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
ERROR: "compile_dist_migrations" exited with 2.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @reactivex/[email protected] build_migrations: `npm-run-all clean_dist_migrations compile_dist_migrations`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @reactivex/[email protected] build_migrations script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
ERROR: "build_migrations" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @reactivex/[email protected] build_all: `npm-run-all compat_build_all clean_dist copy_sources build_cjs build_esm5 build_esm2015 build_esm5_for_rollup build_umd build_types build_legacy_reexport build_migrations generate_packages`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @reactivex/[email protected] build_all script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Metadata
Metadata
Assignees
Labels
No labels