# Problems following quickstart tutorial **URL:** \ **Category:** Build Issues\ **Created:** [September 27, 2025, 11:36pm UTC](https://discuss.emberjs.com/t/problems-following-quickstart-tutorial/21789 "2025-09-27T23:36:36Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![xsember](https://avatars.discourse-cdn.com/v4/letter/x/e19adc/32.png) [@xsember](https://discuss.emberjs.com/u/xsember)\ **Post date:** [September 27, 2025, 11:36pm UTC](https://discuss.emberjs.com/t/problems-following-quickstart-tutorial/21789/1 "2025-09-27T23:36:36Z")
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](https://guides.emberjs.com/release/getting-started/quick-start/) hasn’t been a smooth experience for me. ```auto 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: ```auto 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. ---
**Author:** ![xsember](https://avatars.discourse-cdn.com/v4/letter/x/e19adc/32.png) [@xsember](https://discuss.emberjs.com/u/xsember)\ **Post date:** [September 27, 2025, 11:46pm UTC](https://discuss.emberjs.com/t/problems-following-quickstart-tutorial/21789/2 "2025-09-27T23:46:19Z")
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? ```auto - "@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. ---
**Author:** ![ijlee2](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/ijlee2/32/16190_2.png) [@ijlee2](https://discuss.emberjs.com/u/ijlee2)\ **Post date:** [September 28, 2025, 5:48am UTC](https://discuss.emberjs.com/t/problems-following-quickstart-tutorial/21789/3 "2025-09-28T05:48:30Z")
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](https://github.com/embroider-build/ember-auto-import/pull/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](https://discord.gg/emberjs) 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, ---
**Author:** ![pixelhandler](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/pixelhandler/32/18649_2.png) [@pixelhandler](https://discuss.emberjs.com/u/pixelhandler)\ **Post date:** [September 30, 2025, 8:28am UTC](https://discuss.emberjs.com/t/problems-following-quickstart-tutorial/21789/4 "2025-09-30T08:28:18Z")
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 ---
**Author:** ![darksnake747](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/darksnake747/32/18650_2.png) [@darksnake747](https://discuss.emberjs.com/u/darksnake747)\ **Post date:** [September 30, 2025, 5:53pm UTC](https://discuss.emberjs.com/t/problems-following-quickstart-tutorial/21789/5 "2025-09-30T17:53:03Z")
@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. ---
**Author:** ![ijlee2](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/ijlee2/32/16190_2.png) [@ijlee2](https://discuss.emberjs.com/u/ijlee2)\ **Post date:** [October 1, 2025, 11:25am UTC](https://discuss.emberjs.com/t/problems-following-quickstart-tutorial/21789/6 "2025-10-01T11:25:25Z")
Here’s the issue that I opened in `ember-auto-import`. > > > \## Background > > With \[#662\](https://github.com/embroider-build/ember-auto-import/…pull/662), \`ember-auto-import\` has started to require v2 addons that ship components to list \`@glimmer/component\` in \`dependencies\`, not \`devDependencies\`. I agree with applying a stricter rule, but think there should have been a minor or major release to account for the current addon ecosystem and how package managers may install \`2.10.1\` when \`^2.10.0\` had been specified in \`package.json\`. > > \- Early codemods like \[\`@embroider/addon-blueprint\`\](@embroider/addon-blueprint), \[\`ember-codemod-v1-to-v2\`\](https://github.com/ijlee2/ember-codemod-v1-to-v2), and \[\`create-v2-addon-repo\`\](https://github.com/ijlee2/create-v2-addon-repo) had assumed that it's okay to list \`@glimmer/component\` in \`devDependencies\`. That is, existing v2 addons likely have \`@glimmer/component\` in \`devDependencies\`. > \- Few addon maintainers and consumers are aware of the change in \[#662\](https://github.com/embroider-build/ember-auto-import/pull/662) and will help fix the dependency issue soon. On \[Ember Discourse\](https://discuss.emberjs.com/t/problems-following-quickstart-tutorial/21789), a person who had wanted to try out the Ember tutorial reported running into the error \`Could not find module '@glimmer/component' imported from 'ember-welcome-page/components/welcome-page'\`. \[\`ember-welcome-page\`\](https://github.com/ember-cli/ember-welcome-page/blob/v7.0.2/ember-welcome-page/package.json#L57) hasn't been maintained since May 2023. > \- v1 addons tend to list \`ember-auto-import\` as a dependency (e.g. \[\`ember-intl\`\](https://github.com/ember-intl/ember-intl/blob/v7.4.0/packages/ember-intl/package.json#L49)). As a result, I'm guessing that consuming projects, which depend on one of these v1 addons and one of the v2 addons that didn't list \`@glimmer/component\` in \`dependencies\`, will soon run into errors \`Could not find module '@glimmer/component' imported from\`. If so, the only temporary fix for these projects would be to pin \`ember-auto-import\` to \`2.10.0\` or lower. > > > \## Possible solution > > I'd like to suggest reverting #662 so that we can release \`2.10.2\`, which is in the same state as \`2.10.0\`. Afterwards, recreate #662 and make a minor or major release. I also recommend announcing the breaking change on Ember Discord and https://blog.emberjs.com/ so that people can help update existing v2 addons. Update: Bug has been fixed in `2.11.1`.