If you know how to fix the issue, make a pull request instead.
@types/fs-extra package and had problems.With Typescript 2.9.1
$ tsc -v
Version 2.9.1
Submission 80987f14289ed45458c4ef2bcad5ab8baaeae151 broke support of @types/fs-extra:
$ npm run compile
> [email protected] compile /.../Crunchy
> tsc
node_modules/@types/fs-extra/index.d.ts:210:94 - error TS2694: Namespace '"fs".symlink' has no exported member 'Type'.
210 export function symlink(srcpath: string | Buffer, dstpath: string | Buffer, type: fs.symlink.Type | undefined, callback: (err: NodeJS.ErrnoException) => void): void;
~~~~
node_modules/@types/fs-extra/index.d.ts:212:95 - error TS2694: Namespace '"fs".symlink' has no exported member 'Type'.
212 export function symlink(srcpath: string | Buffer, dstpath: string | Buffer, type?: fs.symlink.Type): Promise<void>;
~~~~
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected] compile: `tsc`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the [email protected] compile script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
I already created https://github.com/DefinitelyTyped/DefinitelyTyped/pull/26381 to fix this issue. In the meantime, you can either pin your @types/fs-extra version or update @types/node.
Any update on above issue
@Roopa-Siddaveerappa As I said above, I created https://github.com/DefinitelyTyped/DefinitelyTyped/pull/26381 so this is no longer my concern. You should subscribe to said pull request if you want to hear any update.
Any update on the issue?
I downgraded to "@types/fs-extra": "5.0.1" to get around the issue.
Most helpful comment
Any update on the issue?
I downgraded to "@types/fs-extra": "5.0.1" to get around the issue.