Fix typo

[andy-hanson]

Mistake from #2102

[andy-hanson]

node_modules/@types/underscore has been in the CircleCI cache for weeks now. Any idea how I can make it go away?

[IllusionMH]

The Rebuild without cache button in the UI will disable the cache for a single build so that you could debug any problems caused by your dependencies.
If such rebuild successfully passes the dependency phase, it will save a new cache which will be used by future builds.

In theory - should work fine after first successful Rebuild without cache.

Normally you will not have to clear the cache permanently, but if you feel that’s what you need, you can just remove the necessary parts of the cache anywhere in your circle.yml’s dependencies section, before the cache is saved:

dependencies:
  post:
    - rm -r ~/.gradle

Or as alternative cache can be removed during build process for some time (even if it will slowdown builds) or switch from npm install to yarn install (I suppose it will use different cache, however not sure if problem not in npm cache itself or with cached by Circle Ci node_modules folder)

Quotes from How cache works

UPD. Any guesses what cache part actually causes problems? If node_modules than we can try to add npm prune before compile steps.

UPD2.

Per-branch cache
Each branch of your project will have a separate cache. If it is the very first build for a branch, the cache from the default branch on GitHub or Bitbucket (normally master) will be used. If there is no cache for master, the cache from other branches will be used.

Probably this might be hint for workaround:

1. Push something to master cache
2. Rebuild without cache
3. New branches will use "working" master cache (in theory - until next cache problem with other dependency)

[adidahiya]

this change is simple enough; I'm comfortable merging without CI