All geek questions in one place

What is the relationship between the angular generator and the angular -fullstack generator?

I am writing this comparison to help people understand the meaning of all this nonsense, and for now it just looks like the generic angular benefits and value are a subset of what you get with the angular -fullstack generator. I filled this material in myself, and I am not an expert, so it is most likely filled with dubious factuality.

But he went through a lot, and no one had screamed yet, so perhaps this is right. If this is the case, it will lead to the logical conclusion that you should always use the generator-angular-complete machine and remove the auxiliary parts if they do not need them. But this cannot be so, as many people still use the generator - angular. I see that the generator-angular-full glass was forked from an angular generator, but then what?

I think I'm missing something. What does an angular generator give people what an angular fullfulstack generator doesn't?

+6
source share
2 answers

I used both generators for a bit now, choosing one over the other really depends on whether you need internal code to provide you with data processing / session management or an API.

generator-angular

  • The official Yeoman generator, this means that it is supported by the yeoman team.
  • More suitable for creating client-side code only.
  • Subgenerators only create client components (angular controllers, routes, and views)
  • It has no deployment generators, but a simple procfile goes a long way.

generator-angular-fullstack

  • Is a fork from the DaftMonk angular generator
  • Suitable for quick launch of a full-fledged application.
  • Uses socket.io to quickly bind data between server / clients
  • Subgenerators create client and server code (API endpoints, models, and even deployment configurations for Heroku and Openshift)
  • Tests are much more thorough, used by PhantomJS, Karma and Protractor
  • When starting a new project, you can add sessions and user management through OpenAuth providers such as Google / Facebook / Twitter, without any problems or use a database schema to store your user data.

Both

  • Create javascript or coffeescript versions for interface code only.
  • Provide build scripts to safely minimize. (angular breaks easily under minimization)
  • Easy to test grunt test
  • Use grunt as a task
  • They are deeply integrated with Bower, and adding dependencies is as easy as pie. (test stage configuration must be updated.)
  • Create a distribution directory with all file thumbnails.
  • These are single page applications, there is only one index.html file, and all routes are done using angular $ location

Demos

+7
source

I am creating generator-ember-fullstack .

The main reason I started this is first I need a complete stack environment.

The first step is to create a project workflow. I select gulp and run the project template.

Then it grows, then I decided to add scaffolding, and I ended up working on generator-ember-fullstack .

The main solution for building generator-ember-fullstack was to have a full stack environment, this includes server forests as well as the client side.

And I really didn't like the grunt-connect plugin, which basically fires a fake server to serve your application. I needed a project, teams for assembly and deployment.

I did not know what to do with the public folder, which is created using grunt build .command.

And with ember there is ember-cli , which is generator-ember on steroids. Again, it lacks the server side, and it is also configured.

But, of course, generator-ember-fullstack only supports nodejs on server. Which is perfect for me.

+1
source

Source: https://habr.com/ru/post/971842/

More articles:


All Articles