Skip to main content

Angular 2–Angular CLI

With the availability of Angular 2, I started experimenting with Angular CLI, a CLI for Angular 2 applications based on the ember-cli project. The project is still young and I encountered a lot of issues along the way.

Here are some tips and lesssons I learned:

  • Update Node to the latest LTS version(you need at least version 4 or later).
  • Run ng in a command prompt with Admin permissions
  • Be patient. The initial installation as well as ng new take a looooong time.
  • On Windows you need to run the build and serve commands with Admin permissions, otherwise the performance is awful.

Some errors I got:

  • “ng is not recognized as an internal or external command”
    • Check that %AppData%\npm is added to the PATH variable.
  • “SyntaxError: Use of const in strict mode.”
    • You are still using an older Node version that doesn’t support some of the new ES2015 features
  • “Error: Cannot find module 'exists-sync'”
    • For an unknown reason NPM still couldn’t find some packages. I installed them manually using the following command
      • npm install --save exists-sync
  • “The Broccoli Plugin: [BroccoliTypeScriptCompiler] failed with:Error: EMFILE: too many open files”
    • This happened when I tried to run ng test. As a workaround you can run ng build first and then run ng test –-watch false. This will run ng test without watching for file changes.
Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more