Import error cloning project | NestJS | Page 1

simple tusk Oct 29, 2024, 12:01 PM

#

I just clonned the project, but, almost every nest import just got those import errors.

It was working yesterday when i pushed the changes, but, for some reason i went to "/common/decorators".
Is it normal?

I'm using Nest v10.0.0

ripe perch Oct 29, 2024, 12:05 PM

#

this is not normal

#

can you share the project?

simple tusk Oct 29, 2024, 12:06 PM

#

It's a private one at my work ://

#

Is there any other way?

#

br?

ripe perch Oct 29, 2024, 12:06 PM

#

what about npm run build? does it works?

ripe perch Oct 29, 2024, 12:07 PM

#

simple tusk br?

yep
se quiser falar em pt, bora pro #português

simple tusk Oct 29, 2024, 12:07 PM

#

nem no ticket não pode?

ripe perch Oct 29, 2024, 12:07 PM

#

aqui é global
A galera tem q entender tbm xD

simple tusk Oct 29, 2024, 12:07 PM

#

got it

ripe perch Oct 29, 2024, 12:07 PM

#

I just tested npx @nestjs/cli@latest new and it worked
So it might be something in your machine

simple tusk Oct 29, 2024, 12:08 PM

#

It's a new one btw

#

A notebook

#

win 11

#

It was the module on CompileOptions

ripe perch Oct 29, 2024, 12:11 PM

#

does your project's directory has the node_modules/@nestjs/common folder?

simple tusk Oct 29, 2024, 12:11 PM

#

Changed it to "module": "NodeNext" and it got fixed, but. it's kinda weird it happened rn because i just worked on it yesterday

#

the last commit was also mine

simple tusk Oct 29, 2024, 12:12 PM

#

ripe perch does your project's directory has the `node_modules/@nestjs/common` folder?

ye

#

Changed to commonjs again and fixed

#

well

#

Guess it fixed itself?

ripe perch Oct 29, 2024, 12:18 PM

#

indeed playing with "module" from tsconfig could make it break
But I guess this is expected due to what those @nestjs/* packages works

#Import error cloning project