https://www.prisma.io/ logo
Join Slack
Powered by
Is there any way to hook Prisma into an existing (...
# prisma-whats-new
p
Is there any way to hook Prisma into an existing (running) 
nodemon
?
d
I think it should work by default. I had changed my start command in package.json to 
"start": "nodemon src/index.js",
Is this what you were looking for? More context?
p
If I run 
yarn dev
I get 
Error: listen EADDRINUSE :::4000
My start is like this: 
dotenv -- nodemon -e ts,graphql -x ts-node src/index.ts
actually
d
It looks like something else is running on 4000. You might want to nuke it with something like 
ps aux | grep "src/index.js" | grep -v grep | awk '{print $2}' | xargs kill -9
Adjust the command acc. to you env or send me output of 
netstat -an | grep 4000
to see what is running on 4000 port
p
ps aux | grep "src/index.js" | grep -v grep | awk '{print $2}'
actually returns nothing
and 
netstat -an | grep 4000
returns the following:
Copy code
tcp6       0      0  ::1.4000               ::1.60732              ESTABLISHED
tcp6       0      0  ::1.60732              ::1.4000               ESTABLISHED
tcp46      0      0  *.4000                 *.*                    LISTEN
The thing is, my playground actually runs correctly, which tells me that Prisma is simply running fine on my local docker
d
Yes, it is already running, which is why it returns "address in use" error with nodemon, once you kill the existing service, it should run with nodemon without any extra work.
p
Hence my question at the start 🙂
So I guess I can’t “attach” to it when it’s already running
d
aha! let me explore it and get back, I understand your question now!
❤️ 1
2 Views
Open in Slack
PreviousNext
Powered by