-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
@types/supertest 4.1.14 is breaking in docker build: Cannot find name 'Blob' #1678
Comments
I think this is our problem on our side... since we are still using node 14 and a cocktail of other old packages in the project |
Same issue. I just lock
|
Can confirm this issue is occurring in a standard build (not docker) as well. Error is a little different. node_modules/@types/superagent/index.d.ts:23:10 - error TS2305: Module '"buffer"' has no exported member 'Blob'. This definitely happened recently. Can also confirm that locking to the "@types/superagent": "4.1.13" did fix the problem, though it's not a great fix in my case. Commenting in case others experience same issue, and so I can watch this unfold. |
It happened with me too. I was running my build on a node 14 environment while I was depending on @types/node of version 13 which does not export "Blob" from "buffer" module. I solved this chaging the dependency version in package.json: FROM "@types/node": "^13.9.1" TO "@types/node": "^14.0.1" |
PR welcome to fix? |
Hey guys, thanks for all the good work your doing.
I had to downgrade a project to @types/supertest 4.1.13 since I was getting a weird problem with typescript while building in docker. It came through in the patch version 4.1.14 since we had carrots on ^. I've learned my lesson and locked all the package versions going forward. So we only update when we want to.
But anyways If your interested:
Here's the docker file. Were using node 14-ish
Then running docker build
docker build . --progress=plain
The error:
I think this is a configuration issue on our side though. I tried to reproduce this on a git repo without our code and the problem is not there.
The text was updated successfully, but these errors were encountered: