Skip to content
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

Nest-Cli Build Error on Ubuntu 18, tsc v 3.7.3 #504

Closed
yusufkhan07 opened this issue Dec 19, 2019 · 2 comments
Closed

Nest-Cli Build Error on Ubuntu 18, tsc v 3.7.3 #504

yusufkhan07 opened this issue Dec 19, 2019 · 2 comments

Comments

@yusufkhan07
Copy link

yusufkhan07 commented Dec 19, 2019

I'm submitting a...


[ ] Regression 
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

I've imported sequelize into my new nestjs project & tried to build but
nest build --tsc fails even though the command tsc builds successfully.

node_modules/sequelize/types/lib/transaction.d.ts:33:14 - error TS1086: An accessor cannot be declared in an ambient context.

33   static get LOCK(): LOCK;
                ~~~~
node_modules/sequelize/types/lib/transaction.d.ts:40:7 - error TS1086: An accessor cannot be declared in an ambient context.

40   get LOCK(): LOCK;
         ~~~~

Found 2 error(s).

Expected behavior

The command nest build --tsc is supposed to use tsc for compilation. As tsc is compiling successfully, nest build --tsc should compile successfully too.
I believe nest build --tsc using an older version of tsc instead of the version 3.7.3.

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

No one like bugs :)

Environment

[System Information]
OS Version     : Linux 5.0
NodeJS Version : v10.17.0
NPM Version    : 6.13.0
[Nest Information]
platform-express version : 6.7.2
common version           : 6.7.2
core version             : 6.7.2

@yusufkhan07
Copy link
Author

After hours of hour, it finally worked with npm upgrade -g @nestjs/cli, previously I was running npm update -g @nestjs/cli instead which didn't fix the issue.

@kamilmysliwiec
Copy link
Member

Thanks for sharing your solution to this issue! This is related to the regression introduced by TypeScript (see microsoft/TypeScript#33939)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants