From angular2-in-memory-web-api to angular-in-memory-web-api about in-memory-web-api HOT 5 CLOSED

Not enough information to answer. I can only assure you that all apps known to us (including all doc samples) are working fine and that all functional changes were additions. You'll have to compare what is different between your old and new app. Look at package.json and inspect node_modules to see that it conforms. Look at your ES import statements. Look for all mentions in your app of angular2-in... ... there should be NONE.

from in-memory-web-api.

@wardbell Thx. I can provide more information, absolutely no problem. I can ensure that there are no other mentions of angular2-in-memory-web-api.

I simply switched from angular2-in-memory-web-api to angular-in-memory-web-api and it's not working anymore. Can you point me an app bootstrapped with angular-cli that use angular-in-memory-web-api?

from in-memory-web-api.

I don't use the CLI, sorry. Not yet. But I see no reason why that should matter. All of the documentation samples use the angular-in-memory-web-api. Please review them.

from in-memory-web-api.

@pmcalabrese One explanation for your output could be that HttpModule is imported after InMemoryWebApiModule.forRoot(InMemoryDataService). In this case you try to call the "real" API endpoint which does not exist.

Always import the InMemoryWebApiModule after the HttpModule to ensure that the XHRBackend provider of the InMemoryWebApiModule supersedes all others.

from in-memory-web-api.

Closing as old and not reproducible. @mentlsve may have provided your answer.

from in-memory-web-api.