Yes it does. I have added enough links that touch on that.
https://github.com/emberjs/data
http://emberjs.com/guides/ember-data-lifecycle/
https://speakerdeck.com/tomdale/30 slides for the video below
http://www.youtube.com/watch?v=djhAsWGOImk Tom Dale - Ember-data
https://speakerdeck.com/tchak/ember-data
In Preventing memory leaks in Backbone.jswarp-drive-data
warp-drive
TypeScript2012–2019
warp-drive-data / warp-drive
warp-drive
WarpDrive is the lightweight data library for ambitious web apps — universal, typed, reactive, and ready to scale.
16Distinct people
19Mentions
0Explicit recommenders
3.2KGitHub stars
What to know before exploring
What it is
WarpDrive is the lightweight data library for ambitious web apps — universal, typed, reactive, and ready to scale.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 11:19:25 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year19 dated mentions
Observed mentions: 2012-02-16 12:20:53 UTC to 2019-01-13 01:38:13 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 6 | 1 | 5 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 10 | 0 | 10 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
WarpDrive is the lightweight data library for web apps —
universal, typed, reactive, and ready to scale.
WarpDrive makes it easy to build scalable, fast, feature
rich applications — letting you ship better experiences more quickly without re-architecting your app or API. WarpDrive is:
🌌 Seamless Reactivity in any Framework
⚡️ Committed to Best-In-Class Performance
💚 Typed
⚛️ Works with any API
🌲 Focused on being as tiny as possible
🚀 SSR Ready
🐹 Built with ♥️ by Ember
Get Started → Guides
Quick Links
Installation
API Docs
Guides
Ember Compatibility
The Big List of Versions
Contributing
Community & Help
RFCs
Team
Blog
Ember Compatibility
The following table lists WarpDrive versions alongside information about
ember compatibility.
Lockstep: the latest version of ember-source at the time of release
Supported: the versions of ember-source the release officially supports
Tested: the versions of ember-source the project tested this release against
Range: the peer-dep range the release states for ember-source
The library is often compatible with a larger range than was officially supported at
the time of release, and we make an effort to test against a larger range than we officially
state is supported. In many cases it will be compatible for a larger range than is shown here.
Where possible, we try to maintain this larger window of support as long as possible, but if
it does become necessary to break compatibility with an older, unsupported release we do not
consider it a breaking change.
The table is generated from this data using the
command pnpm sync-readme-tables.
Status
WarpDrive
Lockstep
Supported
Tested
Range
✅
Canary
6.4
4.8
4.12
5.*
6.*
3.28
4.12
5.12
6.12
3.28.12
>= 4.*
>= 5.*
>= 6.*
✅
Beta
6.4
4.8
4.12
5.*
6.*
3.28
4.12
5.12
6.12
3.28.12
>= 4.*
>= 5.*
>= 6.*
✅
Latest (Stable)
>= 5.3
6.0
6.1
6.2
6.3
4.8
4.12
5.*
6.*
3.28
4.12
5.12
6.12
3.28.12
>= 4.*
>= 5.*
>= 6.*
✅
LTS
>= 5.3
6.0
6.1
6.2
6.3
4.8
4.12
5.*
6.*
3.28
4.12
5.12
6.12
3.28.12
>= 4.*
>= 5.*
>= 6.*
✅
V4 Special Release
(vite support)1
6.3
4.*
5.*
6.*
3.28
4.4
4.8
4.12
5.4
5.8
5.12
6.3
3.28.12
>= 4.*
>= 5.*
>= 6.*
❌
(unsupported)
Prior LTS
4.12.3
4.*
5.*
3.28
4.4
4.8
4.12
5.0
3.28.12
>= 4.*
>= 5.*
❌
(unsupported)
Prior LTS
4.8.6
4.*
3.28
4.4
4.8
3.28.12
>= 4.*
⚠️
(unsupported)
ModelFragments2
4.6.0
3.28
4.*
3.28
4.4
4.5
4.6
3.28.12
>= 4.*
⚠️
(unsupported)
Prior LTS2
4.4.5
3.28
4.*
3.28
4.4
3.28.12
>= 4.*
⚠️
(unsupported)
Prior LTS3
3.28.12
3.*
4.*
3.20
3.24
3.28
>= 3.*
>= 4.*
The Big List of Versions
The table below is generated using the command pnpm sync-readme-tables.
Package
Audience
Canary
Beta
Stable
LTS
V4-Canary
LTS-4-12
warp-drive
🌌
eslint-plugin-warp-drive
🌌
ember-data
🐹
@warp-drive/schema-record
🌌
@warp-drive/holodeck
🌌
@warp-drive/experiments
🌌
@warp-drive/ember
🐹
@warp-drive/diagnostic
🌌
@warp-drive/core-types
🌌
@warp-drive/build-config
🌌
@ember-data/tracking
🌌🐹
@ember-data/store
🌌
@ember-data/serializer
🐹
@ember-data/rest
🌌
@ember-data/request-utils
🌌
@ember-data/request
🌌
@ember-data/model
🐹
@ember-data/legacy-compat
🐹
@ember-data/json-api
🌌🐹
@ember-data/graph
🌌
@ember-data/debug
🐹
@ember-data/codemods
🐹
@ember-data/adapter
🐹
@ember-data/active-record
🌌
Code of Conduct
Refer to the Code of Conduct for community guidelines and inclusivity.
License
This project is licensed under the MIT License.
Footnotes
Special release to support vite builds in apps using 4.x ↩
This version may receive special long-term patches to assist model-fragments users in creating a migration path onto 5.x and off of ModelFragments ↩ ↩2
Special updates have occurred to extend support to ember-source v5 and v6 ↩
Read the full README on GitHubWhat Hacker News says
6 sourcesHave you seen Ember-Data? https://github.com/emberjs/data
In Ember.js 1.0 PrereleaseI've used ember for a little bit. DS is the root namespace of ember-data (https://github.com/emberjs/data), which if you look at the github is pretty clearly still in Alpha and not recommended for production use. I've asked on IRC but haven't been able to get a straight answer out of anyone as to whether ember-data is ready for mass usage or not...
edit: kept trying on IRC and got an answer. Basically Tom Dale said that if you're using rails and ember you should be using ember-data now - should also be using Active Model Serializers gem too.
In The new emberjs.comEmber Data: A data persistence library for Ember.js
1 points · Open discussionI wouldn't say that the sun is setting on Rails-style MVC frameworks, but I do think their role in the ecosystem is going to change. Before, most people could get away with writing the entirety of their app as a single Rails or Django app.
I think the shift first started with the ascendancy of native mobile apps. Now, developers had to seriously start considering their HTTP APIs as first-class citizens and not nice-to-haves. Once that happened, it's not a big leap to realize that treating your web application as somehow different from any of your native clients is a bit, well, insane. You can either choose to write a server that is a mix of JSON API and rendered HTML, with conditionals all about trying to figure out the right thing to render, or you can pull all of that logic out into a stand-alone JavaScript application, with better resp
Read the rest
onsiveness to boot.
I think this approach is a winner. The server guys can focus on building a kick-ass server, and the front-end guys can build an awesome UI without having to muck about in the server bits.
One thing that still blows my mind is how hard it still is to get data from the server to the client. Everyone is writing custom code specific to their app. As the article says:
There's no reason for us to all separately think about these problems and solve them in a million different ways every time we're confronted with them. Aside from the years of wasted time this involves, we've also got a bunch of non-standard and sub-standard APIs to interact with, so all the client code needs to be custom as well and nothing is reusable.
I think this is a huge problem, and Yehuda and I are doing our part to try to solve it. Our Ember Data framework (http://github.com/emberjs/data), by default, assumes certain things, such as the names of your routes and how associations should be loaded. We want to enable people to start building apps right now instead of writing hundreds of lines of JavaScript that are custom to their application, and do it in a sufficiently comprehensive way that you very rarely need to drop down "to the metal." For example, we handle things like mutating associations on the client-side even before a guid has been assigned to a record.
Personally, I'm excited for how this is going to all shake out. I think Rails will continue to be an important piece in the toolchain, but it will no longer be the primary one, and I can't wait to see how it evolves to fill that role.
What do you build your JSON api with? I've been using rails against large javascript applications. It seems like ember.js is a good match against rails (especially with https://github.com/emberjs/data)
In Backbone vs Ember