Skip to content
This repository has been archived by the owner on Nov 25, 2022. It is now read-only.

Fatal error: ENOENT, no such file or directory 'app' #12

Open
reggi opened this issue Nov 25, 2014 · 2 comments
Open

Fatal error: ENOENT, no such file or directory 'app' #12

reggi opened this issue Nov 25, 2014 · 2 comments

Comments

@reggi
Copy link
Contributor

reggi commented Nov 25, 2014

Hey I get this error when there's no app dir, for some reason it's not making the default folder, it does make build though.

thomas@workstation:wheatpaste$ grunt
Running "build-atom-shell-app" task

Downloading releases...
 Downloading atom-shell for darwin
  [====================] 100% 0.0s
 Downloading atom-shell for win32
  [====================] 100% 0.0s

Extracting releases...
>> Extracting darwin
>> Extracting win32

Adding app to releases.
Fatal error: ENOENT, no such file or directory 'app'

Running mkdir app fixes it.

@reggi
Copy link
Contributor Author

reggi commented Nov 25, 2014

I didn't understand how the project should be organized. I had my project at root :)

Unsure where npm modules / package.json should go. Grunt needs to be at root but app-specific in app. Confusing. Explains #11.

I got it working now. I really want:

@hardchor
Copy link

I've got a package.json in root for the build tasks etc. and one in app/package.json for my apm packages (because atom-shell modules need to be built with a different version of node/npm anyway, so that structure makes sense).

@hardchor hardchor mentioned this issue Nov 26, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants