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.

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.

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         ...

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...