Problems following quickstart tutorial

Questions Build Issues
1

I’m sorry to annoy y’all on a Saturday with another tutorial issue, but the issues I’ve found in this forum haven’t been helpful for my situation. Trying to follow the quickstart tutorial hasn’t been a smooth experience for me.

ember-cli: 6.7.0
node: 24.9.0
os: darwin arm64

Installing ember is the easy portion of course, but after trying ember new […] and then initializing the server with npm start (or ember s), all I see in the browser is a blank page and a couple errors in the browser’s console:

Error while processing route: index"Could not find module `@glimmer/component` imported from `ember-welcome-page/components/welcome-page`"

[Error] Error: Could not find module `@glimmer/component` imported from `ember-welcome-page/components/welcome-page`
	onerrorDefault (vendor.js:5833:873)
	trigger (vendor.js:4602)
	(anonymous function) (vendor.js:4903:424)
	invoke (vendor.js:3532:273)
	flush (vendor.js:3527)
	flush (vendor.js:3546:369)
	_end (vendor.js:3576)
	end (vendor.js:3556:565)
	_run (vendor.js:3576:949)
	callback (vendor.js:16171:297)

[Error] Failed to load resource: You do not have permission to access the requested resource.

At first I thought my node version (v22) was outdated so I upgraded that to node v24 using nvm, then re-installed ember-cli. I also tried to delete the node_modules folder and reinstall (rm -rf node_modules && npm install) with no success.

I don’t do a lot of JS code on my day-to-day so I don’t think it’s some sort of cross-contamination from another project which may have messed up my packages or permissions – but of course, I could be wrong (I hope I am).

Any help is appreciated, thank you for reading this far.

1 Like
2

Manually updating the package.json file and downgrading @glimmer/component did the trick, but I’m not sure if that should be the right solution?

-    "@glimmer/component": "^2.0.0",
+    "@glimmer/component": "^1.0.0",

That did the trick. I can see the welcome page now. Now I’m curious on why that works but that’s a whole separate question.

3

Hi, there. I believe the real reason is, when you had run ember new, Ember CLI must have installed ember-auto-import@2.10.1 (the latest version, released 4 days ago).

This version contains a soft-breaking (unsure) change due to ember-auto-import#662, which requires v2 addons (packages) that ship components (e.g. ember-welcome-page) to follow stricter rules when listing their dependencies. ember-welcome-page needs an update in order to follow these new rules.

I can help report the issue to the Ember teams on Discord on Monday. My recommendation for now is to pin the version of ember-auto-import to 2.10.0, e.g. using pnpm.overrides. You can leave the version of @glimmer/component to the latest, i.e. ^2.0.0.

I’m not sure whether node@v24 is fully supported. Feel free to use v20 or v22 for a smooth tutorial experience.

Best,

2 Likes
4

I ran into this issue on a fresh install of ember-cli today

❯ ember -v ember-cli: 6.7.0 node: 22.20.0 os: darwin arm64

1 Like
5

@ijlee2 that fixed my issue. Thanks.

To clarify, in the package.json file, I changed "ember-auto-import": "^2.10.0", to "ember-auto-import": "2.10.0",, then ran an npm install.

That should get you around this issue.

1 Like
6

Here’s the issue that I opened in ember-auto-import.

Update: Bug has been fixed in 2.11.1.

1 Like