Skip to content
This repository was archived by the owner on Feb 26, 2024. It is now read-only.

Migration to @ng-stack/api-mock #254

Open
KostyaTretyak opened this issue Apr 4, 2020 · 2 comments
Open

Migration to @ng-stack/api-mock #254

KostyaTretyak opened this issue Apr 4, 2020 · 2 comments

Comments

@KostyaTretyak
Copy link

KostyaTretyak commented Apr 4, 2020

Obviously, angular-in-memory-web-api has not been developing for a long time. However, as statistics show on npmjs.com, it is downloaded more than 50K times a week.

So I decided that this module is needed by people and should continue to be developed. Please consider an alternative - @ng-stack/api-mock.

@freed00m
Copy link

freed00m commented Apr 5, 2020

Is the in-memory-web-api development really dead?

@KostyaTretyak
Copy link
Author

The last commit in this repository was Jun 20, 2019, but look at this commit

Bump Angular dependencies to 8.x and TypeScript to 3.4.x
Update peerDependencies to version 8 and forward
Add build:lib script to package.json

And before that was the release of 0.8.0 Dec 22, 2018. And even if this module is still being developed, there has been warning:

The in-memory-web-api exists primarily to support the Angular documentation. It is not supposed to emulate every possible real world web API and is not intended for production use.

At the same time, the @ng-stack/api-mock module currently has the functionality many people have been asking for:

  • hierarchical data collection
  • custom primary key named other than id, and this primary key is optional
  • custom search with queryParams
  • store api mock data in localStorage
  • record request and response in the browser console.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants