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
Type Timer not assignable to type Number #68
Comments
It is posible you got node.d.ts definition into project which overloaded standart typescript one for browser. |
This would be viewable under I do have one folder in this directory and it is for node. However, setting up a new node environment using 8.3.0, removing yarn.lock/yarn, still does nothing to change the error or remove the node folder from being automatically added to node_modules when running the So bizarre. |
It has to be some dependency in your package.json. If you can post it here I can help you find it ... |
|
Reproduced, give me some time to debug ... |
Typescript compiler when not defined loads automaticaly all
It will define to Typescript compiler that it should load only specified type modules - and you don't need any. |
Also one minor nitpick "bobril" should be in your "dependencies" and not "devDependencies". |
This looks like new severe problem, I will fix it inside bobril-build so workaround will not be need. |
Latest bobril-build 0.75.0 fixes this automatically. |
Yes! Thank you so much for the fix |
this may help ur issue
|
After recently starting a new project with Bobril (within the last 30 minutes), I am getting the the above error against this line of code:
Bobril/package/index.ts
Line 4233 in 7bce04d
After fishing around for a bit,
waitingForPopHashChange
is a numeric where setTimeout is a timer. Is this a legit error or something perhaps I messed up when installing the project?The text was updated successfully, but these errors were encountered: