Skip to content
This repository was archived by the owner on Apr 8, 2020. It is now read-only.
This repository was archived by the owner on Apr 8, 2020. It is now read-only.

Please provide guidance on how to upgrade #920

Closed

Description

@aligneddev

It would be really helpful if there was instructions provided on how to upgrade from one JavaScriptServices version to the next. I need to update my Aurelia app to pull in the HMR that was just completed.

Activity

  1. SteveSandersonMS commented on May 4, 2017

    @SteveSandersonMS
    Member

    The changes we're making to the libraries don't require you to change your application. The changes to the templates also don't require you to update in any way, since they are templates, rather than something you're taking an ongoing dependency on.

    However I appreciate it's nice to get the features in the latest templates. @MeirionHughes, do you have any advice for people who want to update their Aurelia apps? Failing that, please check the diff in the relevant commits (37df309, e3a8c13, 018a3e6) - applying the same changes to your app is the quickest way to follow along - I'm not aware of any shortcut beyond that. Hope that's OK!

  2. aligneddev commented on May 4, 2017

    @aligneddev
    ContributorAuthor

    That helps, thank you. I was wondering if I could update through a command-line, similar to creating the project with dotnet new aurelia or the yoeman generator.

  3. aligneddev commented on May 4, 2017

    @aligneddev
    ContributorAuthor

    This was pretty easy.
    I overwrote my files from those commits, added in PLATFORM.moduleName( for the routing and a few other places.
    ran npm install after the package.json changes
    then npm update after a run-time error about async not being available.
    Then after that I can add to my html and it shows up in the browser without refreshing!!

    Here's my commit

  4. MeirionHughes commented on May 5, 2017

    @MeirionHughes
    Contributor

    Glad you got it working. There are only a few important things that need to be done really (for anyone still unclear).

    • installing "aurelia-webpack-plugin": "^2.0.0-rc.2",
    • publicPath: '/dist/', in webpack.json
    • new AureliaPlugin({ aureliaApp: 'boot' }) in plugins.
    • you don't need anything in your package.json anymore to describe packages needed by aurelia.
    • the style-loader was removed (for new templates) because Aurelia tries to load them up at runtime if you require the files within your html templates; and they are missing due to the style-bundling - this might be fixed in a later update.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions