jest-haste-map: Haste module naming collision: ng-template
  The following files share their name; please adjust your hasteImpl:
    * <rootDir>/.var/app/com.visualstudio.code/data/vscode/extensions/angular.ng-template-0.1.11/server/package.json
    * <rootDir>/.var/app/com.visualstudio.code/data/vscode/extensions/angular.ng-template-0.1.11/package.json

 FAIL  .var/app/com.visualstudio.code/data/vscode/extensions/mgmcdermott.vscode-language-babel-0.0.22/test.js
  ● Test suite failed to run

    Jest encountered an unexpected token

    This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.

    By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".

    Here's what you can do:
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/en/configuration.html

    Details:

    SyntaxError: /home/alex/.var/app/com.visualstudio.code/data/vscode/extensions/mgmcdermott.vscode-language-babel-0.0.22/test.js: Unexpected token (16:2)

      14 | `;
      15 | const App = () => (
    > 16 |   <StyledComponent>
         |   ^
      17 |     {/* <p>Proper JSX commenting</p> */}
      18 |     <input
      19 |       name="input"

      at Parser.raise (node_modules/@babel/parser/lib/index.js:6322:17)
      at Parser.unexpected (node_modules/@babel/parser/lib/index.js:7638:16)
      at Parser.parseExprAtom (node_modules/@babel/parser/lib/index.js:8799:20)
      at Parser.parseExprSubscripts (node_modules/@babel/parser/lib/index.js:8385:23)
      at Parser.parseMaybeUnary (node_modules/@babel/parser/lib/index.js:8365:21)
      at Parser.parseExprOps (node_modules/@babel/parser/lib/index.js:8252:23)
      at Parser.parseMaybeConditional (node_modules/@babel/parser/lib/index.js:8225:23)
      at Parser.parseMaybeAssign (node_modules/@babel/parser/lib/index.js:8172:21)
      at Parser.parseParenAndDistinguishExpression (node_modules/@babel/parser/lib/index.js:8937:28)
      at Parser.parseExprAtom (node_modules/@babel/parser/lib/index.js:8731:21)

 FAIL  .var/app/com.visualstudio.code/data/vscode/extensions/mgmcdermott.vscode-language-babel-0.0.22/test.jsx
  ● Test suite failed to run

    Jest encountered an unexpected token

    This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.

    By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".

    Here's what you can do:
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/en/configuration.html

    Details:

    SyntaxError: /home/alex/.var/app/com.visualstudio.code/data/vscode/extensions/mgmcdermott.vscode-language-babel-0.0.22/test.jsx: Unexpected token (16:2)

      14 | `;
      15 | const App = () => (
    > 16 |   <StyledComponent>
         |   ^
      17 |     {/* <p>Proper JSX commenting</p> */}
      18 |     <input
      19 |       name="input"

      at Parser.raise (node_modules/@babel/parser/lib/index.js:6322:17)
      at Parser.unexpected (node_modules/@babel/parser/lib/index.js:7638:16)
      at Parser.parseExprAtom (node_modules/@babel/parser/lib/index.js:8799:20)
      at Parser.parseExprSubscripts (node_modules/@babel/parser/lib/index.js:8385:23)
      at Parser.parseMaybeUnary (node_modules/@babel/parser/lib/index.js:8365:21)
      at Parser.parseExprOps (node_modules/@babel/parser/lib/index.js:8252:23)
      at Parser.parseMaybeConditional (node_modules/@babel/parser/lib/index.js:8225:23)
      at Parser.parseMaybeAssign (node_modules/@babel/parser/lib/index.js:8172:21)
      at Parser.parseParenAndDistinguishExpression (node_modules/@babel/parser/lib/index.js:8937:28)
      at Parser.parseExprAtom (node_modules/@babel/parser/lib/index.js:8731:21)

 PASS  ./sum.test.js

Test Suites: 2 failed, 1 passed, 3 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        4.709s
Ran all test suites.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ test: `jest`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/alex/.npm/_logs/2019-04-28T10_50_45_892Z-debug.log
alex@alex-Z:~$