FAQ

Here are some of the most common issues we are aware of that people run into.

What does ng in ng-fullstack stands for?

It stands for next generation, not angular.

Can I use this generator for client only applications?

Sure! Even though the naming suggests it's a fullstack-only generator, there's an option to work only with the client side, no server code generated.

Can I use this generator for server only applications?

Yup, all you have to do is to select server instead of fullstack in the questions asked.

I'm planning to use the generator as a fullstack app, but I want to serve static through a different, is it possible?

Definitely. There's already an option for you to check if you want the server side to serve the static or not. Then, all you have to do is serve the static through, say, nginx and proxy the /api calls to the server.

Do you suggest any IDE for development?

Not really. Chose the one you like the most and speeds up the development of your app. I personally use either Atom or Visual Studio Code, but there are other great ones out there.

I see you have a HTTPS option, should I trust the certs being used?

No. You should have your own certs. The ones used in this generator are meant to help you set up the enviroment for secure development, like setting cookies in secure mode, and this kind of protection. It also helps you to setup HTTP/2 stuff.

What's the reasoning behind the "deep" structure chosen for the generator?

The main reason is: maintainability in long term, in big projects. Some of the generators out there follow the "flat", "featureless" structure, which is a bit like the following:

app
  services
    one-service.ts
    two-service.ts
    three-service.ts

  components
    one-component.ts
    two-component.ts
    three-component.ts

  directives
    one-directive.ts
    two-directive.ts
    three-directive.ts

As you can see, even though that's pretty straight forward, it's pretty hard to keep a track of what's going on when the project gets bigger and bigger. Say that now your controller has a hundred files, the services have models, factories and real services all mixed - it's a big mess - hard to reason about.

So, we're trying to solve the bigger picture by separating by feature, so our structure is as it follows:

app
  one
    services
      one-service.ts
    components
      one-component.ts
    directives
      one-directive.ts

  two
    services
      two-service.ts
    components
      two-component.ts
    directives
      two-directive.ts

  three
    services
      three-service.ts
    components
      three-component.ts
    directives
      three-directive.ts

Now you know exactly what lives within each feature, and, even if you get to hundreds of files inside the one feature, you'll still know it's all about that feature and nothing else.

What about those who want to separate stuff by feature, but not have all those folders?

That's something we've considered and it's coming in 1.10, see #203.

Any chance we get new languages for the server?

Most likely no. Node and Go are the main ones now. Rust might be considered some time ahead, but there's nothing planned.

Any chance we get new framework for the client?

Yes, even though it's not planned yet, React is something we might consider adding.

Any chance we get new framework for the server?

Nope, as of right now we made sure to pick the "best" ones out there, so I don't see any additions for a while.

I want to help, how can I do it?

Oh, that's nice! There's a lot of ways to help: helping others in issues, submiting PRs, adding stuff to the wiki, among many other ways.

Don't be shy, this project is made by the community, for the community - we're all here to help 😄