-
Notifications
You must be signed in to change notification settings - Fork 12.8k
TypeError: path.replace is not a function in ./typescript/lib/typescript.js #26554
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Might be a |
I'm getting this same error when using TypeDoc v0.12.0 with Typescript v3.0.1. Stacktrace:
As for a repo, we are trying to move to project references in this PR: 0xProject/0x-monorepo#991. You can clone it, run |
The failing line in when debugging,
|
I got similar error by using ForkTsCheckerWebpackPlugin. Interestingly the build itself succeeds (it is based on Babel 7 and @babel/preset-typescript).
Versions:
P.S. Ping to fork-ts-checker-webpack-plugin mainteiner @johnnyreilly as per request at #815 |
This seems to be fixed, or at least not affecting anyone anymore |
i am getting the same error PS C:\Users\LENOVO\Desktop\HTML\Registration form\src> node app.js TypeError: path.replace is not a function Node.js v22.6.0 please help me out !! |
@Sourav-1204 that's an error in your code, not TypeScript's. |
Hi, today a had faced with such strange issue. A think this probably of a bug.
Environment:
TypeScript Version: 3.1.0
Webpack Version: 4.15.0
Path Version: 0.12.7
Loaders:
AW-Loader Version: 5.2.0
TS-Loader Version: 4.5.0
(both tested with it, the same scenario):
all package above are installed globally and also locally in project
Code of an Error
Expected behavior:
Must compile app without any errors
Actual behavior:
Broke on Webpack 4 final compilation stage
Related Issues:
no one with typescript
The text was updated successfully, but these errors were encountered: