Closed Jopie01 closed 1 hour ago
Likely you need to set the build config. The vite test app is just testing the happy path (installation via blueprint), I have a few apps building with vite using the individual package approach that don't use ember-data
so there shouldn't be any entanglements there.
In your ember-cli-build file make sure you've done this:
const { setConfig } = await import('@warp-drive/build-config');
let app = new EmberApp(defaults, {});
setConfig(app, __dirname, { compatWith: '3.12' });
AAArrgggghhh, I missed that one :cry: When I saw the config I immediately remembered that I have seen that before and indeed ..... #9461.
Sorry for the noise ...
I'm working towards creating a new app using the latest and greatest developments of embroider, ember and ember-data.
I started with:
Then I uninstalled
ember-data
because I want to use the separate packages as I already do. I manually copied the ember-data packages over to thepackage.json
as dependencies:And did a
pnpm install
.But running this with
pnpm start --host 0.0.0.0
fails with:No idea what's going on, but I looked at PR #9595 which adds a vite test app. There I found that also the
ember-data
package is also installed. That's what I did and then the app build and boots correctly, I can see the welcome page, make changes etc.So why is the
ember-data
package needed? Will it make changes to the new schema and schema-records?