Can I really use it with ember@3.28?

[ro0gr]

I’m currently exploring options to start migrating a number of Ember 3.28 apps to use Warp Drive. The apps use "ember-data-model-fragments", so, based on what I’ve read in the docs, I should try the two-store approach first.

To validate this, I created a plain Ember 3.28 app: warp-drive-test. However, when I install Warp Drive dependencies and run import '@warp-drive/ember/install';, I encounter build errors:

ERROR in ./node_modules/@warp-drive/ember/dist/install.js
Module build failed (from ./node_modules/babel-loader/lib/index.js):
TypeError: /home/runner/work/warp-drive-test/warp-drive-test/node_modules/@warp-drive/ember/dist/install.js: Cannot read properties of undefined (reading 'deprecations')
    at get value [as value] (/home/runner/work/warp-drive-test/warp-drive-test/node_modules/@embroider/macros/src/babel/evaluate-json.js:135:57)
...

Reproduction: https://github.com/ro0gr/warp-drive-test/actions/runs/21084492871/job/60645081471#step:5:30

I also tried enabling Embroider with Webpack, but I encountered a similar build failure: https://github.com/ro0gr/warp-drive-test/actions/runs/21085162748/job/60647054363#step:5:70

As a last resort, I tried Embroider with Vite: ro0gr/warp-drive-test#2. However, the Vite setup prohibits using "ember-fetch", and I don’t know how to make "ember-data" work without it. Is there a workaround? Even if that's the case, I’d still like to know if it’s possible to use this library with the classical build to minimize migration effort. Maybe I'm supposed to start with some older "warp-drive" version, or do I miss something?

[runspired]

I'll see if I can make a demo app soon - it's still possible, though when we test we test with more modern ember-cli.

See

warp-drive/.github/workflows/main.yml

Line 163 in f3eb155

scenario: [ember-lts-5.12, ember-lts-5.8, ember-lts-5.4, ember-lts-4.12, ember-lts-4.8, ember-lts-4.4, ember-lts-3.28]

and https://github.com/warp-drive-data/warp-drive/actions/runs/21046440995/job/60522352896 for a recent run of the test suite.

[runspired]

As a last resort, I tried Embroider with Vite: ro0gr/warp-drive-test#2. However, the Vite setup prohibits using "ember-fetch",

warp-drive/ember-data dropped ember-fetch a long time ago: you definitely wouldn't need that

ERROR in ./node_modules/@warp-drive/ember/dist/install.js
Module build failed (from ./node_modules/babel-loader/lib/index.js):
TypeError: /home/runner/work/warp-drive-test/warp-drive-test/node_modules/@warp-drive/ember/dist/install.js: Cannot read properties of undefined (reading 'deprecations')
    at get value [as value] (/home/runner/work/warp-drive-test/warp-drive-test/node_modules/@embroider/macros/src/babel/evaluate-json.js:135:57)

^ this indicates the build config wasn't set up. For classic builds you'll want some variant of this:

'use strict';
const EmberApp = require('ember-cli/lib/broccoli/ember-app');
const { compatBuild } = require('@embroider/compat');

module.exports = async function (defaults) {
  const { setConfig } = await import('@warp-drive/core/build-config'); 
  const { buildOnce } = await import('@embroider/vite');
  const app = new EmberApp(defaults, {});

  setConfig(app, __dirname, { 
    // this should be the most recent <major>.<minor> version for
    // which all deprecations have been fully resolved
    // and should be updated when that changes
    compatWith: '4.12',
    deprecations: {
      // ... list individual deprecations that have been resolved here
    }
  });

  return compatBuild(app, buildOnce);
};

[ro0gr]

it's still possible, though when we test we test with more modern ember-cli

ah.. it's starting to make sense for me. thank you for the suggestion! I'll try it out and come back.