chore(ci): add node 12

[misterdev]

What kind of change does this PR introduce?
Adds node 12 to Travis and Azure Pipelines and fixes the configuration

Summary
Related to #864
Closes #860

Seems like iltorb doesn't support node 12
We use bundlesize that depends on iltorb, there's an open PR to fix this bundlesize#295 I guess we should wait for it to be merged.

[webpack-bot]

Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon.

[misterdev]

Seems that bundlesize#295 will be merged soon.
@evilebottnawi, if you want, please take a look at the Azure configuration :) Thanks!

[alexander-akait]

All good, thanks

[ematipico]

Azure is failing now

[evenstensberg]

npm ci is probably better, runs fresh install with lockfile

[misterdev]

That's true, I'm just investigating on what broke the Azure CI :)

[misterdev]

• "chore(ci): add stable and improve azure config" (6ca6235)(azure)
• "chore(azure): change to npm ci" (8f02bb3)(azure)

Seems that using npm ci instead of npm install breaks on "macOS node-6"
It fails with sh: rimraf: command not found while executing npm run bootstrap

I'm keeping the old npm install. Any idea on how to fix this is welcome :)

[alexander-akait]

Better always update npm to latest before use npm commands, npm is very buggy

[misterdev]

You are right, on Mac OS it doesn't update npm to the latest version.
But the fix suggested here doesn't work on Linux

I'm going to investigate in the next days :)

[EugeneHlushko]

Hadn't chance to look at CLI for a while now but since last PR i've seen it had gotten so much CI improvements 👏

[EugeneHlushko]

By the way did you try the new WIP PR feature yet @misterdev ? I don't think there is a way to change existing PR into WIP state but for the new ones it's available.

[misterdev]

Hi @EugeneHlushko :) I know about draft pull requests but at the moment Travis doesn't support them :)

[webpack-bot]

@misterdev Thanks for your update.

I labeled the Pull Request so reviewers will review it again.

@EugeneHlushko Please review the new changes.

[misterdev]

Quick update on this:

1. I can't update npm to the latest version (6.9.0) on every platform:

• Currently, we use:

    - task: NodeTool@0
      inputs:
        versionSpec: $(node_version)
      displayName: "Install Node.js"
    - script: |
        npm install -g npm@latest
      displayName: "Install npm"
  

  that doesn't install the latest version on MacOS (89b307a) (azure)

• The other approach proposed in this comment

   - task: Npm@1
       inputs:
         command: custom
         customCommand: i -g npm@latest
      displayName: 'Install latest NPM'
  

  doesn't work giving an EPERM error on Linux (df4928b)(azure) probably because it needs sudo as suggested here :

  On Microsoft-hosted Linux agents, preface the command with sudo, like sudo npm install -g.

2. npm ci doesn't work on MacOS node 6 (6ca6235)(azure), it may be because of (1)

3. bundlesize#295 has been merged, I'm waiting for the updated package to be published to npm

[ematipico]

We can drop node 6. It's dead now. This would solve half of the issue.

[misterdev]

Everything works now, this is ready to be merged!

NB: As suggested by evilebottnawi here, the current azure configuration doesn't update npm to the latest version. The solution proposed doesn't work so I am keeping it unchanged.

[ematipico]

Thank you @misterdev !