Monterey User Manual
  • Introduction
  • What is Monterey
  • Quick guide through the User manual
  • Monterey and module loaders
  • Monterey future plans
  • Installing Monterey
  • Help system
    • Live tour
    • Tooltip based help
  • Features
    • App launcher
    • Aurelia-CLI
    • Dotnet
    • GistRun
    • Error logger
    • Gulp
    • JSPM manager
    • NPM manager
    • Preferences
    • Project info
    • Run
    • Support
    • Task manager
    • Terminal
    • Typings
    • Webpack
    • Workflow manager
  • Creating new applications
    • Aurelia-CLI
      • Default-ESNext
      • Default-TypeScript
      • Custom
    • skeleton-esnext-aspnetcore
    • skeleton-esnext-webpack
    • skeleton-esnext
    • skeleton-typescript-aspnetcore
    • skeleton-typescript-webpack
    • skeleton-typescript
    • GitHub
      • Contact manager tutorial
      • CM tutorial - KendoUI edition
        • Differences from the original version
      • CM tutorial - Materialize edition
        • Differences from the original version
  • Managing existing applications
  • Reaching support
Powered by GitBook
On this page
  • A brief peek in the future of Monterey
  • Important note

Monterey future plans

PreviousMonterey and module loadersNextInstalling Monterey

Last updated 7 years ago

Introduction

A brief peek in the future of Monterey

Important note

This text is provided solely to facilitate the discussions with Monterey users. We are in no way implying that we will do all of these extenstions, nor that we might not add some completely different features - if these turn out to be deemed important by a large enough group of users.

1. Application configuration management

There is a rumor that Monterey started as Aurelia Configuration Tool (aka ACT), application designed to assist Aurelia developers with tedious and complex pedestrian work associated with configuration details of module managers like and module loaders like and .

While Monterey is a lot more complex tool today (see for details), application configuration assistence is one of the key Monterey features (see and for details) in the context of Aurelia applications management.

Here are a few ideas from the general area of configuration management we are considering at the moment

  • Upgrading an existing application to the next version of Aurelia.

  • Downgrading an existing application to some previous version of Aurelia (say for debugging purposes).

  • Analyzing dependencies on other modules and eliminating some that are not used.

2. Deeper and richer integration with other development tools

Current integration level is simple and shallow - see as an example: after the application build step has finished, we could close the Task manager view and click on the Chrome tile to see the running application (Chrome will be passed the URL of http://localhost:5000, specific for the building pipeline of that application.)

New features would include:

  • Invoking VS code, Webstorm IDE or Chrome developer tools for a debugging section directly from Sublime text editor.

  • Expanding the current simple implementation of the application build and run workflow to support specific profiles like application integrator.

  • Integration with

  • ...

3. Complete life-cycle management (aka "DevOps")

While expansion in the direction of item 2 above will reach quite deep, we believe that enabling Monterey to have intelligent integration with will completely fulfill the mantra BUILD, SHIP, RUN.

This feature will equaly support in the context of the planned partnership with several relevant vendors.

npm
jspm
webpack
What is Monterey
npm manager
jspm manager
Image 10 in the Creating new application, skeleton typescript aspnet.core
https://nuclide.io/docs/features/remote/
Docker
kubernetes