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

[BUG] QuickSetup production script throws an error (sh: ts-node: not found) #5

Closed
omrumbakitemiz opened this issue Jan 1, 2022 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@omrumbakitemiz
Copy link

OS: Windows 11 x64
node: 17.3.0
npm: 8.3.0

Steps to produce error:

  • open git-bash
  • run sh setup.sh

after above commands script throws an error on console: sh: ts-node: not found

image

@josephgoksu josephgoksu added the bug Something isn't working label Jan 1, 2022
@josephgoksu josephgoksu self-assigned this Jan 1, 2022
@josephgoksu
Copy link
Owner

It seems like ts-node is missing which means that npm dev dependencies are missing.

https://github.com/joeygoksu/prime-nestjs/blob/3b9bb3244c78b2e26d81e264beceaf2965998294/setup.sh#L38

Temporary solution:

  1. Go into the docker container
  2. Run npm install or yarn command inside of the container
  3. Run the migration script

For the future:

The new version will be released in 1-2 days. (includes new bash script) Thanks for letting us know.

@omrumbakitemiz
Copy link
Author

omrumbakitemiz commented Jan 15, 2022

Any update on new release? 😇

@josephgoksu
Copy link
Owner

It's been a busy month but I will have a chance to update a couple of things next few days.

@josephgoksu josephgoksu changed the title QuickSetup production script throws an error (sh: ts-node: not found) [BUG] QuickSetup production script throws an error (sh: ts-node: not found) Feb 17, 2022
@josephgoksu josephgoksu pinned this issue Feb 17, 2022
@alvindrakes
Copy link

@joeygoksu Love your repo, hope it receives better support and care! You're awesome.

@armensano
Copy link

Still have this error

@josephgoksu
Copy link
Owner

josephgoksu commented Dec 26, 2024

I know it's been ages, but I just fixed the error with 80bdaa5 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants