express-starter | opinionated lightning-fast approach

Basically we have to compile the typescript files from ts to js. Then only we can import into js files. So, I would like to recommend all the backend code should be maintained in either javascript or typescript

• For Typescript: https://github.com/gokulakannant/express-typescript-mongodb-starter
• For Javascript: https://github.com/GetStream/node-express-mongo-api

You can use any other starter projects like above

I was having the same issue, it was caused because my NgModules classes had the "export default" modifier. Look if your modules had the export default and remove the "default" modifier as it's not supported by ngc.

It's the structure of your query. The query should be structured much like you would in GraphiQL such as:
mutation { updateUserName(id: 1, name: "du") { id name } }

Hence, your code should look something like this, with the mutation keyword as the first thing in your query before your opening brace { :

When you're using loadChildren, it's called "Lazy Loading" and in total it helps us to decrease the startup time. Modules that are lazily loaded will only be loaded when the user navigates to their routes.

For more info about "Lazy Loading": https://angular-2-training-book.rangle.io/handout/modules/lazy-loading-module.html

The fact you are seeing the call firing twice in the chrome dev tools means that the issue is on the client side.

My suggestion is to subscribe to the call instead of assigning the returned observable to a local property. Then you can make a break point at entry point of you method that calls the service. Once hit, have a look at the call stack to see who is firing the call. I would guess that you will see the OnInit method calling getSettings() twice. To which case I would assume that your component is being created twice for some reason in your application.

Hit npm start in the project directory. The script associated is declared in the package.json under scripts [...]

I think there is a solution undergoing now.

it is on ngrx/store-devtools

kudos to robertohuertasm@github

You can remove devtools to workaround this issue before they push a new release.