Tell user that they are missing packages when launching server

[jonabrams]

Tell user that they are missing packages when launching server

[vicentedealencar]

synth install -b could have an alias to synth npm install, this makes so much sense.

[JonAbrams]

Could you make another issue for that and expand what you mean?

On Fri, Jun 6, 2014 at 2:37 AM, Vicente de Alencar
[email protected] wrote:

synth install -b could have an alias to synth npm install, this makes so much sense.

Reply to this email directly or view it on GitHub:
#2 (comment)

[DanDeMicco]

Hey Jon,

This is Dan from the meetup @ Box. I just started looking at the project and see you have a way to generate a sample project. After you generate the project you have to cd to it, then do this:

cd my_app # Change the working directory to the root of your new web app
synth install -b # Install third-party back-end packages (using npm)
synth install -f # Install third-pary front-end packages (using bower)

This seems to differ from all node projects I have seen. I was wondering why you went this approach, rather than putting a package.json and bower.json file at the root of the project, and running npm install (like every other node and angular project, that I have seen at least) which you can then add a postinstall script to also run the bower install after?

You could also make it so that when you run synth new my_app it will automatically install dependencies I am sure.

[JonAbrams]

This seems to differ from all node projects I have seen. I was wondering why you went this approach

Yup. One of the goals of Synth was to simplify the project and keep the front-end code and back-end code in separate directories. You're right that most projects have a package.json and bower.json in their root, but to me this seems confusing and messy. That's why all Synth projects just have 3 top folders: back, front, and synth.json. The stuff in back defines the back-end, the stuff in front is what is served up to the browser.

You could also make it so that when you run synth new my_app it will automatically install dependencies I am sure.

The intention was that I wanted it to be a separate step to force people to learn the install command/step, since it's rather important. Lately though I've been thinking of it doing the install automatically. I noticed Rails has started doing that now too.

[mikaelhm]

I just experienced this issue. Even worse it printed No synth app detected (missing synth.json)., which was kinda misleading :)

[JonAbrams]

I'm thinking it'd be good enough to just check if back/node_modules and front/bower_components exist. Thoughts?

On Thu, Aug 14, 2014 at 3:06 PM, Mikael Møller [email protected]
wrote:

I just experienced this issue. Even worse it printed No synth app detected (missing synth.json)., which was kinda misleading :)

Reply to this email directly or view it on GitHub:
#2 (comment)

[mikaelhm]

No, I think we need show missing packages.

Yesterday, I had installed using synth install -b but I was using a package I forgot to install a new package, and suddenly i got this message:

No synth app detected (missing synth.json).

[JonAbrams]

Well, that's a new bug, probably introduced by this commit

[JonAbrams]

Probably the way to solve this is to:

1. Check for a synth.json, and if not show the current message: No synth app detected (missing synth.json).
2. Try to load the app, and if there's a MODULE_NOT_FOUND error, then print Could not load all modules. Make sure you run 'synth install -b'

[mikaelhm]

Yes, that would be a great solution..