bugfix release, infrastructure changes

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

bugfix release, infrastructure changes

Herby Vojčík
Hello everyone!

There is a new bugfix release of amber, 0.14.15 out there.

The CLI compiler amberc (along with its grunt task) starts to move away
from generating node executables itself and towards doing the compile
task only (the "linker" is now requirejs). For that, amber-dev bumped to
0.6.0, amber-cli itself has a new version (though nothing new there,
from functionality PoV, but it is now built using requirejs) 0.14.11 and
of course, grunt-init-amber which defines how new project is created,
has changed in its Gruntfile.js.

First change is, test runner is now composed not by amberc task as
before, but by requirejs task.

Second, newly created projects now possess _three_ (not two) loadsets:

  - *deploy.js* which is same as before - just the app and the core of
amber, to build the production package
  - *testing.js* new one, which should include all the tests that are to
be run by automatic test runner. Majority of test should be in this
category, but there may be some tests which explicitly need to be run
inside browser environment - UI etc. Those should not be included. The
testing.js loadset is used to build CLI testrunner, which can be run by
`grunt test` or `npm test` and you can use it in your CI.
  - *devel.js* contains everything you need to develop inside browser UI
- so full dev version of amber, the legacy IDE, examples, plus you
should include those tests from your app that absolutely need browser
environment here.

There is also another file included by default, named 'config-node.js'.
In this file, you can include specific patches for node environment (it
is used to build the above-mentioned test runner for CLI). The basic
patches are already included, you can add your own ones should you need
them (for example, to disable some UI-only library from loading,
similarly to the way how jQuery is disabled there already).

Herby

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: bugfix release, infrastructure changes

Herby Vojčík
Oh yeah.

You upgrade cli by

   npm install -g amber-cli

The new cli specifies bower etc. as sibling dependencies, so you no more
need to do `npm install -g amber-cli bower grunt-cli`. Just amber-cli
and it installs them beside itself if they are missing.

To upgrade projects, first upgrade them to 0.14.14, then make new
project from 0.14.15 and migrate the code (mechanically), and distrubute
packages into new loadsets (by hand); if you made changed to your
original Gruntfile, try to apply them to the new one (which is different
a bit).

Herby Vojčík wrote:

> Hello everyone!
>
> There is a new bugfix release of amber, 0.14.15 out there.
>
> The CLI compiler amberc (along with its grunt task) starts to move away
> from generating node executables itself and towards doing the compile
> task only (the "linker" is now requirejs). For that, amber-dev bumped to
> 0.6.0, amber-cli itself has a new version (though nothing new there,
> from functionality PoV, but it is now built using requirejs) 0.14.11 and
> of course, grunt-init-amber which defines how new project is created,
> has changed in its Gruntfile.js.
>
> First change is, test runner is now composed not by amberc task as
> before, but by requirejs task.
>
> Second, newly created projects now possess _three_ (not two) loadsets:
>
> - *deploy.js* which is same as before - just the app and the core of
> amber, to build the production package
> - *testing.js* new one, which should include all the tests that are to
> be run by automatic test runner. Majority of test should be in this
> category, but there may be some tests which explicitly need to be run
> inside browser environment - UI etc. Those should not be included. The
> testing.js loadset is used to build CLI testrunner, which can be run by
> `grunt test` or `npm test` and you can use it in your CI.
> - *devel.js* contains everything you need to develop inside browser UI -
> so full dev version of amber, the legacy IDE, examples, plus you should
> include those tests from your app that absolutely need browser
> environment here.
>
> There is also another file included by default, named 'config-node.js'.
> In this file, you can include specific patches for node environment (it
> is used to build the above-mentioned test runner for CLI). The basic
> patches are already included, you can add your own ones should you need
> them (for example, to disable some UI-only library from loading,
> similarly to the way how jQuery is disabled there already).
>
> Herby
>

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.