yes and your ember-source (the actual ember core code) is at 3.11 also. I think you installed the updater but didn’t actually update it.
and it mentioned
npm install -g ember-cli-update ember-cli-update
that ran successfully
This installs ember-cli-update as a global npm package, but then you need to run ember-cli-update like so: ember-cli-update [--to=3.16] the bracket part is only necessary if you want to specify the version you’re going to (and you shouldn’t actually type the brackets btw).
This does a bunch of magic and merges the new blueprints into your app, but you’ll need to resolve some git conflicts usually to cover any customizations you’ve made to the ember project files that get updated.
so does 3.16 handle components differently? I noticed the fresh project doesn’t have a components directory in the templates directory?
I also noticed that the template for a component is in a directory called components ?
I also noticed when you run ember generate component it mentions: ** skip app/components/people-list.js**
also:
tip to add a class, run ember generate component-class people-list
ember generate component people-list
installing component
create app\components\people-list.hbs
skip app/components/people-list.js
tip to add a class, run `ember generate component-class people-list`
installing component-test
create tests\integration\components\people-list-test.js
so the .js for the component’s .hbs is now generated separately as a class?
Ember 3.15 marked the “release” (basically it’s now the default) of Ember Octane which includes a bunch of new features landed throughout the 3.x series.
one of the new features is a greater emphasis on template-first components. So by default the component generator actually only generates a template, and adding a js class is encourage on an “only if needed” basis
Octane also supports “template co-location” meaning templates are placed inline with the component and not in templates/components
There are now two varieties of components: Classic and Glimmer. Glimmer components are now encouraged as the new default and eventually I think Ember classic components will be deprecated. There are a lot of differences between the two but if you’re following the quickstart hopefully they won’t be as noticeable vs updating a large old app.
Anyway hope that helps clear things up a little bit. Checking out the “upgrade guide” might help sort out the new features too.
I’m still learning new stuff every day so it’s a weird balance. On the one hand learning stuff upfront can definitely make your life easier but on the other hand sometimes the best way to learn is to jump in and get your hands dirty. Good luck!
quick question: how to I get new applications to start at the newer versions of ember-cli emb-babel etc etc…it seems like I need to run a upgrade install after I generate a new app ?
If I’m understanding the question you should just have to update your ember-cli global version (npm install -g ember-cli) to the latest, and then it will use its default app blueprint to create the new app. So each project has ember-cli listed as a dependency, but you also have a globally installed version of ember-cli on your machine in your node runtime environment that determines what new projects are initialized with.
Okay I think I got it… I deleted the ember cmd batch file and the ember ps1 powershell file from my nodejs installation location then ran the npm install -g ember-cli --to=3.16…