The Ember project has recently released version 3.14 of Ember.js, Ember Data, and Ember CLI. This kicks off the 3.15 beta cycle for all sub-projects. We encourage our community (especially addon authors) to help test these beta builds and report any bugs before they are published as a final release in six weeks' time. The ember-try addon is a great way to continuously test your projects against the latest Ember releases.
In the first section there are initial instructions on what you need to do, however, there is no text giving the specifics:
With the exception of an updated release of @glimmer/component, the steps to try out the Octane preview remain the same in 3.14 as they were in 3.13:
Add the following packages if they aren't already present at this version:
Disable legacy behavior by setting the following feature flags:
Specify the Octane edition in .ember-cli.js by adding the following lines to the beginning of the file:
If you have an .ember-cli file instead of an .ember-cli.js file, you can convert it by renaming it to .ember-cli.js, then taking the existing JSON object and assigning it to module.exports. For example, if you have an .ember-cli file with:
The equivalent .ember-cli.js file would be:
So then I thought that maybe I could find that information by clicking on the link underneath all of the missing information, i.e.
If you need more information on how to migrate away from these legacy features, check out the [Octane release plan](https://emberjs.com/2019/08/15/octane-release-plan.html) blog post.
Boy, that is weird. I am missing the codeblocks. I’m using the latest version of Firefox on Ubuntu. Cleared the history and cache and they still don’t show up. Then I tried Chrome and had the same problem: no code blocks. I wonder why you can see them and I can’t.
Regarding the “Page Not Found” - you are right in that it is missing the “blog” at the beginning of the URL. To get there I clicked on the link in this page => it needs to have the “blog” prepended to the front of the URL.
Thanks for the reply. (And I still don’t understand what is happening. )
Hey, I am really excited to move my existing app to Octane. However, I was wondering if there will be any code modes to help with the conversion to the “octane way”? Things like:
)