#Why is trigger.dev trying to scandir my Downloads folder??

1 messages · Page 1 of 1 (latest)

unkempt flower
#

I'm trying to run the basic example workflow and getting the following error:

tchan@MacBook-Pro trigger % pwd
/Users/tchan/Code/Trigger.dev/Test/src/trigger

tchan@MacBook-Pro trigger % npx trigger.dev@latest dev

Trigger.dev (3.0.6)

Key: Version | Task | Run

X Error: EPERM: operation not permitted, scandir '/Users/tchan/Downloads'

quasi dock
#

That's definitely a bug, my guess is that we're looking for a file (like package.json maybe) and it traverses up until it finds it.

But @keen jewel will have a better answer as he built this.

keen jewel
#

That's weird

#

Can you run that again with --log-level debug

#

And DM me the output?

keen jewel
#

Do you have a package.json in Trigger.dev/Test?

unkempt flower
#

No, I just started with an empty folder and ran the quick start steps.

keen jewel
#

Yea you'll need a package.json:

npm init -y
npm add @trigger.dev/sdk@latest
npm add @trigger.dev/build@latest -D
unkempt flower
#

That worked! Thanks Eric!

#

It might be a good idea to update your Quick start guide with these extra steps?

keen jewel
#

Yea it's meant to be a guide for adding to an existing project but that isn't too clear. I'll make a note of it

unkempt flower
#

Ya, it definitely wasn't clear to me. I assumed you'd want to create a new project just for your Triggers so you can easily manage/debug them separately from your other projects (e.g. web/mobile app, etc...)

keen jewel
#

You don't have to do that, it's actually meant to be "embedded" inside an existing project