Blog Blog
Home
Home/WebStorm/Running JavaScript Tests with Karma in WebStorm

Running JavaScript Tests with Karma in WebStorm

Posted on by Ekaterina Prigara

Updated on August, 8th 2016.

With every update of WebStorm we try to add support for modern technologies and tools that help make your development experience even better. In WebStorm 7 we introduced support for Karma – a simple and flexible tool for executing JavaScript tests, developed by the AngularJS team.

Here is some basic info about Karma integration in WebStorm:

  • It uses a local server to run the tests in the selected browsers installed on your computer;
  • It can run tests written with the use of Jasmine, QUnit, or Mocha, or write a simple adapter to use any other framework you like;
  • It works with the istanbul code coverage engine.

Here is a short guide about using Karma in WebStorm. Check out the screencast or read the post to start using Karma.

http://youtu.be/oyWW_V4wALs

Initial configuration

To start using Karma, make sure that Node.js is installed on your computer. You can install Karma globally or locally using npm. The recommended approach is to install Karma locally in the project’s directory.

Then you need to add a Karma configuration file to your project. In this configuration file you should specify the testing framework you are going to use, and select browsers for testing.

You can generate it with the following command:
karma init karma.conf.js
or add it manually.

karma-init

Adding Karma Run/Debug configuration

Now you need to create a new Karma Run/Debug Configuration that will allow you to simply run or debug your tests anytime in WebStorm.

Right-click on the karma.conf.js file in the Project view and select Create “karma.conf.js” option to create a new Run/Debug configuration based on this config file.

create-karma-config

Alternatively, you can add Karma configuration from the Edit configurations dialog that can be found in the Run menu. Don’t forget to specify the path to the Karma configuration file.

karma-config

Running tests

To start running your tests, select this new Run/Debug configuration from the drop-down list on the right of the IDE navigation bar and click on the green Run button. Or hit Alt-Shift-F10 on Windows and Linux or Ctrl-Alt-R on OS X and select the configuration in the Run popup.

run-popup

WebStorm will run Karma and soon the test results will appear in a nice visual format in the Karma tool window.

karma-tool-window

You can navigate from the test result to its code, check statistics for the tests execution, and make HTML reports from it.

Rerun tests on changes

Please note that WebStorm disables autoWatch in Karma configuration. You can enable running tests automatically on changes by WebStorm by clicking Toggle auto-test icon on the left side of the Karma tool window: test will be run 10 seconds after your code was changed, if there are no syntax errors.

You can also rerun your tests with the shortcut Alt-Shift-R on Windows and Linux or Ctrl-Cmd-R on OS X.

Run with coverage

WebStorm provides support for the istanbul code coverage engine that is used by Karma. Install node module karma-coverage and add coverage settings in the Karma configuration file, and then simply click the Run with coverage button to get the report of the coverage of your code with tests.

Debugging tests

With WebStorm you can also debug Karma test. Once the Karma Run/Debug configuration is created, put the breakpoints in your code and hit the Debug button next to the drop-down list of configurations to start the debug session. Once the breakpoint is hit, you can step through the code and evaluate expessions.

Your WebStorm Team

#karma #testing
Comments below can no longer be edited.

63 Responses to Running JavaScript Tests with Karma in WebStorm

  1. Andrew Martin says:

    October 4, 2013

    Brilliant and slick integration. A dream to use for TDD. Thanks!

  2. Jonas says:

    October 5, 2013

    Wow, awesome integration! 🙂

    • Tomas says:

      October 17, 2014

      Let’s do that for meteor. In 0.9.4 we should be able to run tests on background and then use similar parser to show the output. Would be great;)

  3. Kees de Kooter says:

    October 7, 2013

    Is it possible to let WS watch file changes and fire the tests on change?

    • Ekaterina Prigara says:

      October 7, 2013

      You can enable Auto-test (it’s on the left in the Test Run window): the tests will be run in 10 seconds after the change is made if there is no syntax errors.

      • Zach says:

        October 8, 2013

        Why does it wait 10 seconds? When I am using Karma’s autowatch directly the feedback is much quicker.

        • Ekaterina Prigara says:

          October 8, 2013

          So far we’ve decided that 10 seconds is the right timeout – not too frequent. We are thinking now about adding an option to configure it.

          • Yngvar Kristiansen says:

            October 12, 2013

            Please do. IMO, it makes the most sense to get immediate feedback from tests as soon as you save your file.

          • BS says:

            October 17, 2013

            +1 for adding a setting (at least).

            10 seconds seems too much for real TDD. I write a test, hit CTRL+S and have to wait 10 seconds to ensure that the test fails. Then I have to wait another 10 seconds after I change the source code to ensure that it passes the tests. It really disrupts and slows down the workflow.

            I don’t hit CTRL+S that super often anyway — only after actually having written that couple of lines that make the test.

            I think that WebStorm’s integration with tests might be the best on the market regardless of that delay, but I’d really appreciate if it was slower. Think of all those guys who try their best to do real TDD!

            • Ekaterina Prigara says:

              October 18, 2013

              Hello,
              As you might now WebStorm automatically takes care of saving your files, you don’t have to press CTRL+S to save them – that’s out vision that we actually follow. That is why in our Karma integration we disable Karma’s autoWatch feature – saving file doesn’t trigger tests to run.
              To Rerun tests there are 2 options:
              1. Use a shortcut Rerun tests: it’s set to ALT+SHIFT+R by default – you can reassign it to CTRL+S if you want
              2. Enable Auto-test option: tests will be rerun after file is changed if there is no syntax errors. In WebStorm 7.0.1 (it will be available in couple of days as an automatic update and is available now as a Release candidate ) you can configure the delay for auto-test.

              We believe that this way we make our integration more advanced since you have more options to rerun tests and you can have them running automatically on change.

  4. PhpStorm 7 Web Toolkit Series – npm, Karma, istanbul | JetBrains PhpStorm Blog says:

    October 21, 2013

    […] and allows us to choose between JSTestDriver and Karma for running unit tests. Have a look at the WebStorm blog for more […]

  5. George Ivanov says:

    October 30, 2013

    I’m loving the new Karma integration. However, the Karma config created above will have to list *all* test files. During test development, though, I’m only interested in running only a single test spec (not all). Is there any way to do that in WS7?

    The reason for this is i have a test suite that is pretty large, and when developing the current tests, I only want to run the tests in the current test file, not all of the files included in the karma.conf.js.

    • Sergey Simonchik says:

      October 31, 2013

      Alas, Karma doesn’t support running only a single test spec (not all). WS7 can’t improve the situation without fixing it on Karma core side.
      AFAIK, the recommended to run just one spec is to use iit(“should do something”, function(){}); ddescribe(“component”, function(){});

  6. George Ivanov says:

    October 30, 2013

    I’m also having issues making PhantomJS browser work with WS7. My karma.confg.js works just fine with Chrome as a browser. With ‘PhantomJS’ as a browser and adding “karma-phantomjs-launcher’ into the plugins, I do see the the karma server started, however, no tests are run. The “Tests Run” view says “Waiting for browser capturing…” but no tests are executed.

    • George Ivanov says:

      October 31, 2013

      The problem turned out to be Node. According to the following post:

      https://github.com/karma-runner/karma/issues/558

      Karma has a known issue running with PhantomJS on Node 0.10.10. After upgrading to 0.10.21, my jasmine tests are running fine in the PhantomJS browser.

      • Eugene says:

        March 8, 2014

        So you have configuration WebStorm + Karma + Jasmine? Do you have a blog where you could do article, that explains whole setup or maybe you could share a link for tutorial you might have used. Thanks.

        • Ekaterina Prigara says:

          March 9, 2014

          Yes, WebStorm supports Karma. Please have a look at the educational video in this blog post as well as a short tutorial.

  7. Patrick Podenski says:

    November 30, 2013

    Latest release of WS appears to run tests with no delay when the auto-test is selected. Where can the delay be configured?

  8. Patrick Podenski says:

    November 30, 2013

    Ideally the delay would start to count down when there is no typing activity – right now it runs test every few key strokes which is excessive.

  9. Thor A. Lange says:

    December 3, 2013

    I am using IntelliJ Idea (with a commercial license) an was wondering whether this feature about running Karma tests directly from within the IDE i available in Idea too? Although I am running 12.1.6 it seems that the option is not currently available.

  10. Testing with angular, Karma and Webstorm | Bjoern's Blog says:

    December 30, 2013

    […] a good points to start are a blog article about karma testing in webstorm 7 and of course the jetbrains confluence […]

  11. Thé #15 – Jean Laurent de Morlhon – Les Tests JavaScript avec Karma | Une tasse de thé says:

    January 19, 2014

    […] Karma avec Grunt : https://github.com/karma-runner/grunt-karma#running-tests Karma avec WebStorm : http://blog.jetbrains.com/webstorm/2013/10/running-javascript-tests-with-karma-in-webstorm-7/ Karma avec Jenkins : […]

  12. Brian says:

    January 27, 2014

    This is great! thanks.

    I was trying to create an debug some javascript. I was trying to bring in a module in my test like this:

    var example = require(‘example’);

    but I get an error saying “Uncaught ReferenceError: require is not defined”. Is there something more I need to configure to do this?

    Thank you.
    Brian

    • Ekaterina Prigara says:

      January 28, 2014

      Brian,

      Please have a look at one of our recent posts on Node.js development in WebStorm: http://blog.jetbrains.com/webstorm/2014/01/getting-started-with-node-js-in-webstorm/

      • Oliver says:

        January 28, 2014

        Don’t think this is answered. Karma appears to rely on browser testing only. And since the Webstrom offers a Testsuite integration for Karma only, m current conclusion is: WebStorm does not support any test framework for server side JavaScript.

        Unless someone finds a way around the Browser only constraint.

        • Ekaterina Prigara says:

          January 28, 2014

          I missed a line in Brian’s comment where he mentions “tests”. But in any case when you’re working with Node.js you need to have it configured in a way described in the linked post.

          Oliver, you are right that Karma integration is for client-side JavaScript testing only.
          For testing Node.js in WebStorm one should use Mocha test framework that was added in WebStorm 7.0.2 update (http://blog.jetbrains.com/webstorm/2013/11/webstorm-7-0-2-is-available/) or Nodeunit.

        • Vance Feldman says:

          March 11, 2014

          you can use Karma with node/grunt PhantomJS (browserless head) to do testing.

  13. gcoder says:

    March 16, 2014

    I had to install the cli to get the karma command line in windows

    npm install -g karma-cli

    • Ekaterina Prigara says:

      March 17, 2014

      To use Karma integration in WebStorm you don’t really need Karma-cli

  14. Run Karma test suite in Intellij | Thoughts on code says:

    May 1, 2014

    […] Run Karma test suite in Intellij […]

  15. AngularJS-Learning | Nisar Khan says:

    May 2, 2014

    […] Running JavaScript tests with Karma in WebStorm 7 […]

  16. xamgreen says:

    September 19, 2014

    Hey,

    do you have an advice for me, what i can try? My Webstorm runs /path/to/karma/karma /path/to/script/intellijServer.js … and some option. Than its writes “Unknown command “/home/max/.WebIde70/config/plugins/js-karma/js_reporter/karma-intellij/lib/intellijServer.js”.” and fails. The file exists i’d checked that. Do you have any Idea what that could be? My Versions are
    Karma: 0.12.23
    PhpStorm 7.1.4, Build #PS-133.1777

    By the way, great article!

    Greez, xamgreen

    • Sergey Simonchik says:

      September 22, 2014

      Hi,
      Sorry, can’t reproduce the issue with karma 0.12.23 and PhpStorm 7.1.4. Tests run OK for me.
      Could you please file an issue in the http://youtrack.jetbrains.com/issues/WEB#newissue and provide there details (your karma.conf.js, “Karma Server” tab output)?
      Thanks.

  17. My Present Stack and Preferred Development Environment | The Ultimate Laravel + AngularJS guide says:

    January 7, 2015

    […] My decision to switch to JetBrains was also swayed by the fact that they had a dedicated IDE for javascript development. You can even integrate KarmaJS into WS, see here: Running Javascript tests on Webstorm. […]

  18. SHUBHOJIT ROY says:

    April 20, 2016

    Integration of Karma in WebStorm is awesome. And, Auto-test does work, but it caches the code, thus the re-run does not run the latest version of code. One needs to stop and restart the Karma server to get fresh code (including specs).
    I did find a workaround (workarounds are always ugly, thus not mentioning) for now, but would expect the IDE to handle this on its own.
    for reference, I’m using WeStorm 2016.1.1

    • Sergey Simonchik says:

      April 22, 2016

      It mostly depends on how karma runs tests. There is a probably similar issue https://youtrack.jetbrains.com/issue/WEB-21308 (here test files are compiled to dist/ folder and then karma runs the compiled files). If it’s your case, please upvote, otherwise please provide more details about your environment. Thanks.

    • Tobias Henöckl says:

      June 24, 2016

      Same issue here, could you share your ugly workaround, please? 😉

      • Chris Deely says:

        August 13, 2016

        The workaround for me was to edit the file below and change ‘refresh’ to ‘true’
        /Applications/WebStorm.app/Contents/plugins/js-karma/js_reporter/karma-intellij/lib/intellijRunner.js

        • steve lutz says:

          August 16, 2016

          Brilliant. I’ve given up a few times on using the karma runner for this reason (needing to stop and start the karma server).

        • Will Humphreys says:

          October 23, 2016

          Thank you. That also worked for me.

        • Tim Furry says:

          March 17, 2017

          Bless you for posting this…I’ve been fighting this for weeks and could not figure out what was going on. This has fixed the caching issue.

  19. antoine says:

    February 15, 2017

    is it possible to run a subset of the unit tests ?

  20. zeev rosental says:

    October 1, 2017

    hi!

    is there anyway to generate the html results file through cli?

    thanks!

    • Ekaterina Prigara says:

      October 2, 2017

      Sorry, don’t know how it could be done in CLI (and not in WebStorm). Probably you need this plugin: https://www.npmjs.com/package/karma-html-reporter

      • zeev rosental says:

        October 2, 2017

        I wish that html report was half as good as the one webstorm creates 🙂

  21. Don Lazov says:

    October 13, 2017

    So I have a nodejs, angular 4 application and I can get WebStorm to run the tests but it fails to hit any breakpoints in either the spec or the application code that is called.

    @angular/cli: 1.4.5
    node: 6.11.4
    os: linux x64 (Centos 7.4.1708 (Core))
    WebStorm 2017.2.4
    Google Chrome (with JetBrains IDE Support 2.0.9 plugin) 61.0.3163.100 (Official Build) (64-bit)

    Using Run/Debug Configuration for Karma:
    Configuration file is set to local karma-conf.js
    Browsers to start (empty)
    Node interpreter is pointing to the correct version
    Karma package is pointing to the correct location

    In my Karma Server output I see:

    95% emitting
    13 10 2017 13:10:27.637:INFO [Chrome 61.0.3163 (Linux 0.0.0)]: Connected on socket viK9hkJT0qe7GVjOAAAB with id 48941768
    13 10 2017 13:10:27.643:INFO [PhantomJS 2.1.1 (Linux 0.0.0)]: Connected on socket lFemxVz8G1r8EYYhAAAA with id 17080500

    CollectionEditComponent
    convertResourcesToResources
    ✓ should convert Book materials
    …
    ✓ should convert NON WPE Web Material with no displayableUrl
    TOTAL: 12 SUCCESS

    Chrome 61.0.3163 (Linux 0.0.0): Executed 6 of 1126 (skipped 1120) SUCCESS (7.105 secs / 3.677 secs)
    PhantomJS 2.1.1 (Linux 0.0.0): Executed 6 of 1126 (skipped 1120) SUCCESS (8.307 secs / 5.697 secs)
    TOTAL: 12 SUCCESS

    /home/dlazov/.nvm/versions/node/v6.11.4/bin/node /home/dlazov/devtools/WebStorm-172.4155.35/plugins/js-karma/js_reporter/karma-intellij/lib/intellijRunner.js –karmaPackageDir=/home/dlazov/projects/collections-app-ui/node_modules/karma –serverPort=9876 –urlRoot=/

    Process finished with exit code 0

    Test runs fine but no breakpoints hit when running with Shift+F9 (debug mode).

    Here is my karma.config.js:

    // Karma configuration file, see link for more information
    // https://karma-runner.github.io/0.13/config/configuration-file.html

    module.exports = function(config) {
    config.set({
    basePath: ”,
    frameworks: [‘jasmine’, ‘@angular/cli’],
    plugins: [
    require(‘karma-jasmine’),
    require(‘karma-chrome-launcher’),
    require(‘karma-jasmine-html-reporter’),
    require(‘karma-coverage-istanbul-reporter’),
    require(‘karma-phantomjs-launcher’),
    require(‘karma-spec-reporter’),
    require(‘@angular/cli/plugins/karma’),
    require(‘karma-coverage’)
    ],
    client: {
    clearContext: false // leave Jasmine Spec Runner output visible in browser
    },
    coverageIstanbulReporter: {
    reports: [‘html’, ‘lcovonly’],
    fixWebpackSourcePaths: true
    },
    angularCli: {
    environment: ‘dev’
    },
    files: [
    // Include a Material theme in the test suite. Note without this ‘mock’ theme the tests will spawn a warning.
    { pattern: ‘./node_modules/@angular/material/prebuilt-themes/indigo-pink.css’, included: true, watched: true },
    { pattern: ‘./src/test.ts’, watched: false }
    ],
    preprocessors: {
    ‘./src/test.ts’: [‘@angular/cli’],
    ‘app/**/!(*.spec).js’: [‘coverage’]
    },
    coverageReporter: {
    reporters: [
    {type: ‘json’, dir: ‘coverage’}
    ]
    },
    reporters: [‘progress’, ‘kjhtml’, ‘spec’, ‘coverage’, ‘coverage-istanbul’],
    port: 9876,
    colors: true,
    logLevel: config.LOG_INFO,
    autoWatch: true,
    browsers: [‘Chrome’, ‘PhantomJS’],
    singleRun: false,
    specReporter: {suppressSkipped: true},
    mime: { ‘text/x-typescript’: [‘ts’,’tsx’] }
    });
    };

    Why does WebStorm not hit breakpoints for nodejs/angular apps?

  22. Don Lazov says:

    October 16, 2017

    Oksana,

    I tried 2017.3 EAP and the same problem persist (not hitting any breakpoints). Please note that this is for our production app, which is a nodejs/angular 4 app that has been highly customized. However with that said I was able within WebStorm to create a default new angular cli project and change the app name from app to name and set breakpoints and when I run the test suite it does hit the breakpoints.

    I can’t provide a sample project since this is running a production application from my company, but here is the log from my production app that fails to hit breakpoints:

    2017-10-16 09:06:54,844 [ 0] INFO – #com.intellij.idea.Main – —————————————————— IDE STARTED ——————————————————

    2017-10-16 09:06:54,847 [ 3] INFO – #com.intellij.idea.Main – IDE: WebStorm (build #WS-173.3188.31, 12 Oct 2017 04:48)

    2017-10-16 09:06:54,847 [ 3] INFO – #com.intellij.idea.Main – OS: Linux (3.10.0-693.2.2.el7.x86_64, amd64)

    2017-10-16 09:06:54,847 [ 3] INFO – #com.intellij.idea.Main – JRE: 1.8.0_152-release-1024-b5 (JetBrains s.r.o)

    2017-10-16 09:06:54,847 [ 3] INFO – #com.intellij.idea.Main – JVM: 25.152-b5 (OpenJDK 64-Bit Server VM)

    2017-10-16 09:06:54,848 [ 4] INFO – #com.intellij.idea.Main – JVM Args: -agentpath:/home/dlazov/devtools/WebStorm-173.3188.31/bin/libyjpagent-linux64.so=disablealloc,delay=10000,probe_disable=*,sessionname=WebStorm2017.3 -Xbootclasspath/a:/home/dlazov/devtools/WebStorm-173.3188.31/lib/boot.jar -Xms128m -Xmx750m -XX:ReservedCodeCacheSize=240m -XX:+UseConcMarkSweepGC -XX:SoftRefLRUPolicyMSPerMB=50 -ea -Dsun.io.useCanonCaches=false -Djava.net.preferIPv4Stack=true -XX:+HeapDumpOnOutOfMemoryError -XX:-OmitStackTraceInFastThrow -XX:MaxJavaStackTraceDepth=-1 -Dawt.useSystemAAFontSettings=lcd -Dsun.java2d.renderer=sun.java2d.marlin.MarlinRenderingEngine -XX:ErrorFile=/home/dlazov/java_error_in_WEBIDE_%p.log -XX:HeapDumpPath=/home/dlazov/java_error_in_WEBIDE.hprof -Didea.paths.selector=WebStorm2017.3 -Djb.vmOptionsFile=/home/dlazov/devtools/WebStorm-173.3188.31/bin/webstorm64.vmoptions -Didea.platform.prefix=WebStorm

    2017-10-16 09:06:54,848 [ 4] INFO – #com.intellij.idea.Main – ext: /home/dlazov/devtools/WebStorm-173.3188.31/jre64/lib/ext: [cldrdata.jar, dnsns.jar, jaccess.jar, jfxrt.jar, localedata.jar, meta-index, nashorn.jar, sunec.jar, sunjce_provider.jar, sunpkcs11.jar, zipfs.jar]

    2017-10-16 09:06:54,848 [ 4] INFO – #com.intellij.idea.Main – JNU charset: UTF-8

    2017-10-16 09:06:54,878 [ 34] INFO – #com.intellij.idea.Main – JNA library (64-bit) loaded in 30 ms

    2017-10-16 09:06:55,333 [ 489] INFO – .intellij.idea.IdeaApplication – WM detected: Metacity (Marco)

    2017-10-16 09:06:55,771 [ 927] INFO – llij.ide.plugins.PluginManager – Cannot find optional descriptor js-nashorn-support.xml

    2017-10-16 09:06:55,772 [ 928] INFO – llij.ide.plugins.PluginManager – Cannot find optional descriptor ./jest-coverage.xml

    2017-10-16 09:06:55,909 [ 1065] INFO – llij.ide.plugins.PluginManager – Cannot find optional descriptor uml-java-support.xml

    2017-10-16 09:06:55,909 [ 1065] INFO – llij.ide.plugins.PluginManager – Cannot find optional descriptor uml-properties-support.xml

    2017-10-16 09:06:56,197 [ 1353] INFO – llij.ide.plugins.PluginManager – 56 plugins initialized in 721 ms

    2017-10-16 09:06:56,198 [ 1354] INFO – llij.ide.plugins.PluginManager – Loaded bundled plugins: ASP (0.1), AngularJS (173.3188.31), CSS Support (173.3188.31), CVS Integration (11), CoffeeScript (2.0), Cucumber.js (0.1), Dart (173.3188.31), Docker integration (173.3188.31), EJS (173.3188.31), EditorConfig (173.3188.31), File Watchers (173.3188.31), Gherkin (999.999), Git Integration (8.1), GitHub (173.3188.31), HTML Tools (2.0), Haml (173.3188.31), Handlebars/Mustache (173.3188.31), IDEA CORE (173.3188.31), IntelliLang (8.0), Java Server Pages (JSP) Integration (1.0), JavaScript Debugger (1.0), JavaScript Intention Power Pack (0.9.4), JavaScript Support (1.0), Karma (173.3188.31), Less support (173.3188.31), LiveEdit (173.3188.31), Mercurial Integration (10.0), Meteor (173.3188.31), Node.js Remote Interpreter (173.3188.31), NodeJS (173.3188.31), Perforce Integration (2.0), PhoneGap/Cordova Plugin (173.3188.31), Polymer & Web Components (999.999), Pug (ex-Jade) (173.3188.31), QuirksMode (173.3188.31), REST Client (173.3188.31), Refactor-X (2.01), Remote Hosts Access (0.1), SSH Remote Run (0.1), Sass support (173.3188.31), Settings Repository (173.3188.31), Spy-js (173.3188.31), Stylus support (999.999), Subversion Integration (1.1), Task Management (1.0), Terminal (0.1), TextMate bundles support (173.3188.31), Time Tracking (1.0), UML Support (1.0), Vagrant (173.3188.31), Vue.js (173.3188.31), W3C Validators (2.0), XPathView + XSLT Support (4), YAML (173.3188.31), Yeoman (173.3188.31), tslint (173.3188.31)

    2017-10-16 09:06:56,687 [ 1843] INFO – ij.components.ComponentManager – com.intellij.openapi.components.impl.ServiceManagerImpl initialized in 150 ms

    2017-10-16 09:06:56,858 [ 2014] INFO – ellij.vfs.persistent.FSRecords – Marking VFS as corrupted: ‘/home/dlazov/.WebStorm2017.3/system/caches/names.dat’ does not exist

    2017-10-16 09:06:56,860 [ 2016] INFO – ellij.util.io.PagedFileStorage – lower=100; upper=500; buffer=10; max=705

    2017-10-16 09:06:56,896 [ 2052] INFO – ij.components.ComponentManager – com.intellij.openapi.vfs.newvfs.persistent.PersistentFSImpl initialized in 85 ms

    2017-10-16 09:06:56,912 [ 2068] INFO – pl.local.NativeFileWatcherImpl – Starting file watcher: /home/dlazov/devtools/WebStorm-173.3188.31/bin/fsnotifier64

    2017-10-16 09:06:56,928 [ 2084] INFO – pl.local.NativeFileWatcherImpl – Native file watcher is operational.

    2017-10-16 09:06:56,929 [ 2085] INFO – ij.components.ComponentManager – com.intellij.openapi.vfs.impl.local.LocalFileSystemImpl initialized in 118 ms

    2017-10-16 09:06:56,933 [ 2089] INFO – ij.components.ComponentManager – com.intellij.openapi.vfs.PlatformVirtualFileManager initialized in 126 ms

    2017-10-16 09:06:57,141 [ 2297] INFO – pi.util.registry.RegistryState – Registry values changed by user:

    2017-10-16 09:06:57,141 [ 2297] INFO – pi.util.registry.RegistryState – dumb.aware.run.configurations = true

    2017-10-16 09:06:57,160 [ 2316] INFO – ij.components.ComponentManager – com.intellij.openapi.util.registry.RegistryState initialized in 78 ms

    2017-10-16 09:06:57,510 [ 2666] INFO – ij.components.ComponentManager – com.intellij.openapi.fileTypes.impl.FileTypeManagerImpl initialized in 345 ms

    2017-10-16 09:06:57,537 [ 2693] INFO – ij.components.ComponentManager – com.intellij.openapi.keymap.impl.KeymapManagerImpl initialized in 15 ms

    2017-10-16 09:06:57,946 [ 3102] INFO – ij.components.ComponentManager – com.intellij.openapi.actionSystem.impl.ActionManagerImpl initialized in 424 ms

    2017-10-16 09:06:57,963 [ 3119] INFO – ij.components.ComponentManager – com.intellij.openapi.editor.impl.EditorFactoryImpl initialized in 443 ms

    2017-10-16 09:06:57,968 [ 3124] INFO – .history.utils.LocalHistoryLog – local history version mismatch (was: 0, expected: 6), rebuilding…

    2017-10-16 09:06:57,968 [ 3124] INFO – .history.utils.LocalHistoryLog – FS has been rebuild, rebuilding local history…

    2017-10-16 09:06:57,992 [ 3148] INFO – ij.components.ComponentManager – com.intellij.history.integration.LocalHistoryImpl initialized in 28 ms

    2017-10-16 09:06:58,004 [ 3160] INFO – ij.components.ComponentManager – com.intellij.openapi.command.impl.UndoManagerImpl initialized in 11 ms

    2017-10-16 09:06:58,138 [ 3294] INFO – ij.components.ComponentManager – com.intellij.ide.ui.laf.LafManagerImpl initialized in 130 ms

    2017-10-16 09:06:58,204 [ 3360] INFO – ij.components.ComponentManager – com.intellij.util.net.HttpConfigurable initialized in 32 ms

    2017-10-16 09:06:58,439 [ 3595] INFO – til.net.ssl.CertificateManager – Default SSL context initialized

    2017-10-16 09:06:58,441 [ 3597] INFO – ij.components.ComponentManager – com.intellij.util.net.ssl.CertificateManager initialized in 236 ms

    2017-10-16 09:06:58,538 [ 3694] INFO – ij.components.ComponentManager – com.intellij.ide.SystemHealthMonitor initialized in 96 ms

    2017-10-16 09:06:58,576 [ 3732] INFO – ij.components.ComponentManager – com.intellij.openapi.wm.impl.WindowManagerImpl initialized in 27 ms

    2017-10-16 09:06:58,584 [ 3740] INFO – ij.components.ComponentManager – com.intellij.openapi.wm.impl.FocusManagerImpl initialized in 39 ms

    2017-10-16 09:06:58,608 [ 3764] INFO – rains.ide.BuiltInServerManager – built-in server started, port 63343

    2017-10-16 09:06:58,609 [ 3765] INFO – ij.components.ComponentManager – com.intellij.ide.IdeTooltipManager initialized in 24 ms

    2017-10-16 09:06:58,630 [ 3786] INFO – ij.components.ComponentManager – com.intellij.ide.SaveAndSyncHandlerImpl initialized in 21 ms

    2017-10-16 09:06:58,638 [ 3794] INFO – gs.impl.UpdateCheckerComponent – channel: release

    2017-10-16 09:06:58,640 [ 3796] INFO – gs.impl.UpdateCheckerComponent – channel forced to ‘eap’

    2017-10-16 09:06:58,692 [ 3848] INFO – ij.components.ComponentManager – com.intellij.openapi.updateSettings.impl.UpdateCheckerComponent initialized in 61 ms

    2017-10-16 09:06:58,725 [ 3881] INFO – ij.components.ComponentManager – com.intellij.openapi.actionSystem.ex.QuickListsManager initialized in 28 ms

    2017-10-16 09:06:58,746 [ 3902] INFO – ij.components.ComponentManager – com.intellij.openapi.vcs.changes.actions.migrate.MigrateDiffApplicationComponent initialized in 16 ms

    2017-10-16 09:06:59,018 [ 4174] INFO – il.indexing.FileBasedIndexImpl – Index exts enumerated:257

    2017-10-16 09:06:59,036 [ 4192] INFO – il.indexing.FileBasedIndexImpl – Index scheduled:18

    2017-10-16 09:06:59,037 [ 4193] INFO – ij.components.ComponentManager – com.intellij.util.indexing.FileBasedIndexImpl initialized in 287 ms

    2017-10-16 09:06:59,075 [ 4231] INFO – ij.components.ComponentManager – com.intellij.psi.stubs.SerializationManagerImpl initialized in 29 ms

    2017-10-16 09:06:59,184 [ 4340] INFO – tellij.psi.stubs.StubIndexImpl – All stub exts enumerated:135

    2017-10-16 09:06:59,188 [ 4344] INFO – tellij.psi.stubs.StubIndexImpl – stub exts update scheduled:3

    2017-10-16 09:06:59,188 [ 4344] INFO – ij.components.ComponentManager – com.intellij.psi.stubs.StubIndexImpl initialized in 150 ms

    2017-10-16 09:06:59,211 [ 4367] INFO – ij.components.ComponentManager – com.intellij.openapi.roots.impl.libraries.LibraryKindLoader initialized in 15 ms

    2017-10-16 09:06:59,236 [ 4392] INFO – ij.components.ComponentManager – com.intellij.execution.ExecutorRegistryImpl initialized in 20 ms

    2017-10-16 09:06:59,265 [ 4421] INFO – ij.components.ComponentManager – com.intellij.ide.a.e initialized in 27 ms

    2017-10-16 09:06:59,323 [ 4479] INFO – ij.components.ComponentManager – org.intellij.plugins.relaxNG.ApplicationLoader initialized in 58 ms

    2017-10-16 09:06:59,363 [ 4519] INFO – ij.components.ComponentManager – com.intellij.remoteServer.impl.configuration.deployment.DeployToServerConfigurationTypesRegistrar initialized in 39 ms

    2017-10-16 09:06:59,398 [ 4554] INFO – ij.components.ComponentManager – org.intellij.lang.xpath.xslt.impl.XsltConfigImpl initialized in 26 ms

    2017-10-16 09:06:59,610 [ 4766] INFO – ij.components.ComponentManager – com.intellij.javascript.JSSupportLoader initialized in 211 ms

    2017-10-16 09:06:59,676 [ 4832] INFO – ij.components.ComponentManager – org.jetbrains.plugins.textmate.TextMateApplicationComponent initialized in 61 ms

    2017-10-16 09:06:59,677 [ 4833] INFO – plication.impl.ApplicationImpl – 78 application components initialized in 4208ms

    2017-10-16 09:06:59,742 [ 4898] INFO – .intellij.idea.IdeaApplication – App initialization took 13127 ms

    2017-10-16 09:06:59,753 [ 4909] INFO – .openapi.application.Preloader – Finished preloading com.intellij.ide.ui.OptionsTopHitProvider$Activity@6a1b14

    2017-10-16 09:07:00,478 [ 5634] INFO – ij.psi.stubs.StubUpdatingIndex – Following new file types will be indexed:Spacebars,SCSS,TypeScript,ECMAScript 6,Flow,XML,Jade,JSP,Literate CoffeeScript,JavaScript,Less,HTML,CoffeeScript,EJS,JSX Harmony,Vue.js,Stylus,Sass,Handlebars/Mustache,TypeScript JSX,CSS,ActionScript

    2017-10-16 09:07:01,189 [ 6345] INFO – pl$FileIndexDataInitialization – Initialization done:2143

    2017-10-16 09:07:01,304 [ 6460] INFO – ij.components.ComponentManager – com.intellij.openapi.components.impl.ServiceManagerImpl initialized in 19 ms

    2017-10-16 09:07:01,330 [ 6486] INFO – ij.components.ComponentManager – com.intellij.openapi.command.impl.UndoManagerImpl initialized in 20 ms

    2017-10-16 09:07:01,347 [ 6503] INFO – ij.components.ComponentManager – com.intellij.openapi.vcs.impl.FileStatusManagerImpl initialized in 17 ms

    2017-10-16 09:07:01,370 [ 6526] INFO – ij.components.ComponentManager – com.intellij.openapi.vfs.encoding.EncodingProjectManagerImpl initialized in 22 ms

    2017-10-16 09:07:01,413 [ 6569] INFO – ij.components.ComponentManager – com.intellij.openapi.wm.impl.ToolWindowManagerImpl initialized in 42 ms

    2017-10-16 09:07:01,451 [ 6607] INFO – ij.components.ComponentManager – com.intellij.openapi.roots.impl.ProjectRootManagerComponent initialized in 17 ms

    2017-10-16 09:07:01,472 [ 6628] INFO – ij.components.ComponentManager – com.intellij.psi.impl.PsiManagerImpl initialized in 44 ms

    2017-10-16 09:07:01,516 [ 6672] INFO – ij.components.ComponentManager – com.intellij.openapi.fileEditor.impl.PsiAwareFileEditorManagerImpl initialized in 91 ms

    2017-10-16 09:07:01,520 [ 6676] INFO – ij.components.ComponentManager – com.intellij.openapi.fileEditor.impl.IdeDocumentHistoryImpl initialized in 96 ms

    2017-10-16 09:07:01,589 [ 6745] INFO – ij.components.ComponentManager – com.intellij.openapi.module.impl.ModuleManagerComponent initialized in 64 ms

    2017-10-16 09:07:01,609 [ 6765] INFO – exImpl$StubIndexInitialization – Initialization done:419

    2017-10-16 09:07:01,630 [ 6786] INFO – ij.components.ComponentManager – com.intellij.openapi.vcs.impl.ProjectLevelVcsManagerImpl initialized in 109 ms

    2017-10-16 09:07:01,686 [ 6842] INFO – pl.projectlevelman.NewMappings – VCS Root: [] – []

    2017-10-16 09:07:01,689 [ 6845] INFO – pl.projectlevelman.NewMappings – VCS Root: [Git] – [/home/dlazov/projects/collections-app-ui]

    2017-10-16 09:07:01,689 [ 6845] INFO – ij.components.ComponentManager – com.intellij.openapi.vcs.impl.VcsDirectoryMappingStorage initialized in 58 ms

    2017-10-16 09:07:01,835 [ 6991] INFO – ij.components.ComponentManager – com.intellij.openapi.vcs.changes.ChangesViewManager initialized in 138 ms

    2017-10-16 09:07:01,892 [ 7048] INFO – ij.components.ComponentManager – com.intellij.openapi.vcs.changes.ChangeListManagerImpl initialized in 200 ms

    2017-10-16 09:07:01,894 [ 7050] INFO – ij.components.ComponentManager – com.intellij.openapi.vcs.impl.VcsFileStatusProvider initialized in 204 ms

    2017-10-16 09:07:01,899 [ 7055] INFO – ij.components.ComponentManager – com.intellij.openapi.vcs.impl.LineStatusTrackerManager initialized in 209 ms

    2017-10-16 09:07:01,923 [ 7079] INFO – ij.components.ComponentManager – com.intellij.openapi.vcs.changes.shelf.ShelvedChangesViewManager initialized in 20 ms

    2017-10-16 09:07:01,946 [ 7102] INFO – ij.components.ComponentManager – com.intellij.psi.impl.PsiDocumentManagerImpl initialized in 11 ms

    2017-10-16 09:07:01,977 [ 7133] INFO – ij.components.ComponentManager – com.intellij.codeInsight.daemon.impl.DaemonCodeAnalyzerImpl initialized in 24 ms

    2017-10-16 09:07:02,015 [ 7171] INFO – ij.components.ComponentManager – com.intellij.profile.codeInspection.ProjectInspectionProfileManager initialized in 35 ms

    2017-10-16 09:07:02,041 [ 7197] INFO – ij.components.ComponentManager – com.intellij.codeInsight.daemon.impl.DaemonListeners initialized in 64 ms

    2017-10-16 09:07:02,080 [ 7236] INFO – ij.components.ComponentManager – com.intellij.codeInsight.daemon.impl.GeneralHighlightingPassFactory initialized in 38 ms

    2017-10-16 09:07:02,103 [ 7259] INFO – ij.components.ComponentManager – com.intellij.codeInsight.navigation.CtrlMouseHandler initialized in 17 ms

    2017-10-16 09:07:02,338 [ 7494] INFO – ij.components.ComponentManager – com.intellij.xdebugger.impl.XDebuggerManagerImpl initialized in 216 ms

    2017-10-16 09:07:02,358 [ 7514] INFO – ij.components.ComponentManager – com.intellij.javaee.PsiExternalResourceNotifier initialized in 11 ms

    2017-10-16 09:07:02,442 [ 7598] INFO – ij.components.ComponentManager – com.intellij.tasks.impl.TaskManagerImpl initialized in 74 ms

    2017-10-16 09:07:02,523 [ 7679] INFO – ij.components.ComponentManager – com.intellij.lang.javascript.linter.JSLinterEditorPanelCreator initialized in 74 ms

    2017-10-16 09:07:02,538 [ 7694] INFO – ij.components.ComponentManager – org.angularjs.service.Angular2HighlightingPassFactory initialized in 14 ms

    2017-10-16 09:07:02,543 [ 7699] INFO – ellij.project.impl.ProjectImpl – 99 project components initialized in 1805 ms

    2017-10-16 09:07:02,645 [ 7801] INFO – ij.components.ComponentManager – com.intellij.openapi.roots.impl.ModuleRootManagerComponent initialized in 57 ms

    2017-10-16 09:07:02,659 [ 7815] INFO – le.impl.ModuleManagerComponent – 1 module(s) loaded in 114 ms

    2017-10-16 09:07:02,782 [ 7938] INFO – .openapi.application.Preloader – Finished preloading com.intellij.openapi.actionSystem.impl.ActionPreloader@a4a2d1d

    2017-10-16 09:07:02,931 [ 8087] INFO – j.ide.script.IdeStartupScripts – 0 startup script(s) found

    2017-10-16 09:07:03,384 [ 8540] INFO – .openapi.application.Preloader – Finished preloading com.intellij.ide.ui.search.SearchableOptionPreloader@4612d453

    2017-10-16 09:07:03,769 [ 8925] WARN – pl.local.NativeFileWatcherImpl – The current inotify(7) watch limit is too low. More details.

    2017-10-16 09:07:03,771 [ 8927] WARN – api.vfs.impl.local.FileWatcher – The current inotify(7) watch limit is too low. More details.

    2017-10-16 09:07:03,780 [ 8936] INFO – .openapi.application.Preloader – Finished preloading com.intellij.codeInsight.completion.CompletionPreloader@473886c2

    2017-10-16 09:07:04,966 [ 10122] INFO – rojectCodeStyleSettingsManager – Initialized from default code style settings.

    2017-10-16 09:07:05,421 [ 10577] INFO – .diagnostic.PerformanceWatcher – Pushing properties took 842ms; general responsiveness: ok; EDT responsiveness: ok

    2017-10-16 09:07:05,563 [ 10719] INFO – .TypeScriptLibraryProviderImpl – Start refreshing typescript libraries

    2017-10-16 09:07:07,396 [ 12552] INFO – tartup.impl.StartupManagerImpl – OpenFilesActivity run in 2951ms under project opening modal progress

    2017-10-16 09:07:07,535 [ 12691] INFO – tartup.impl.StartupManagerImpl – InitToolWindowsActivity run in 128ms under project opening modal progress

    2017-10-16 09:07:07,663 [ 12819] INFO – .diagnostic.PerformanceWatcher – Post-startup activities under progress took 3264ms; general responsiveness: ok; EDT responsiveness: 2/4 sluggish, 1/4 very slow

    2017-10-16 09:07:08,620 [ 13776] INFO – tartup.impl.StartupManagerImpl – /home/dlazov/projects/collections-app-ui/.idea case-sensitivity: expected=true actual=true

    2017-10-16 09:07:08,625 [ 13781] WARN – api.vfs.impl.local.FileWatcher – Project files cannot be watched (are they under network mount?)

    2017-10-16 09:07:08,626 [ 13782] INFO – tartup.impl.StartupManagerImpl – unwatched roots: [/home/dlazov/projects/collections-app-ui]

    2017-10-16 09:07:08,626 [ 13782] INFO – tartup.impl.StartupManagerImpl – manual watches: [/home/dlazov/projects/collections-app-ui]

    2017-10-16 09:07:08,823 [ 13979] INFO – git4idea.GitVcs – Git version: 2.14.2.0 (UNIX)

    2017-10-16 09:07:08,851 [ 14007] INFO – son.PackageVersionRangeMatcher – Matching 74 done in 265 ms, not matched: [(express range:^4.16.1 version:4.15.3), (instana-nodejs-sensor range:^1.27.0 version:1.26.5), (ajv range:^5.2.3 version:5.2.0)]

    2017-10-16 09:07:09,071 [ 14227] INFO – pl.projectlevelman.NewMappings – VCS Root: [Git] – [/home/dlazov/projects/collections-app-ui]

    2017-10-16 09:07:10,392 [ 15548] INFO – tor.impl.FileEditorManagerImpl – Project opening took 9792 ms

    2017-10-16 09:07:10,435 [ 15591] INFO – .diagnostic.PerformanceWatcher – Indexable file iteration took 5012ms; general responsiveness: ok; EDT responsiveness: 3/6 sluggish, 1/6 very slow

    2017-10-16 09:07:10,443 [ 15599] INFO – indexing.UnindexedFilesUpdater – Unindexed files update started: 8626 files to update

    2017-10-16 09:07:10,638 [ 15794] INFO – .TypeScriptLibraryProviderImpl – End refreshing typescript libraries

    2017-10-16 09:07:11,141 [ 16297] INFO – ndex.PrebuiltIndexProviderBase – Using prebuilt sdk-stubs from /home/dlazov/.WebStorm2017.3/system/index/.persistent/prebuilt/JavaScript/sdk-stubs.input

    2017-10-16 09:08:09,642 [ 74798] INFO – .diagnostic.PerformanceWatcher – Unindexed files update took 59199ms; general responsiveness: ok; EDT responsiveness: ok

    2017-10-16 09:08:09,819 [ 74975] INFO – tartup.impl.StartupManagerImpl – Some post-startup activities freeze UI for noticeable time. Please consider making them DumbAware to do them in background under modal progress, or just making them faster to speed up project opening.

    2017-10-16 09:08:09,819 [ 74975] INFO – tartup.impl.StartupManagerImpl – Activity run in 156ms on UI thread

    2017-10-16 09:10:45,801 [ 230957] INFO – cript.karma.server.KarmaServer – Karma server 1380784316 started successfully: /home/dlazov/.nvm/versions/node/v6.11.4/bin/node /home/dlazov/devtools/WebStorm-173.3188.31/plugins/js-karma/js_reporter/karma-intellij/lib/intellijServer.js –karmaPackageDir=/home/dlazov/projects/collections-app-ui/node_modules/karma –configFile=/home/dlazov/projects/collections-app-ui/karma.conf.js

    2017-10-16 09:10:53,704 [ 238860] INFO – cript.karma.server.KarmaServer – Processing Karma event configFile {“autoWatch”:true,”basePath”:”/home/dlazov/projects/collections-app-ui”,”browsers”:[“Chrome”,”PhantomJS”],”hostname”:”localhost”,”urlRoot”:”/”,”protocol”:”http:”,”webpack”:false}

    2017-10-16 09:12:00,545 [ 305701] INFO – cript.karma.server.KarmaServer – Processing Karma event browserConnected {“id”:”90248077″,”name”:”Chrome 61.0.3163 (Linux 0.0.0)”,”isAutoCaptured”:true}

    2017-10-16 09:12:00,992 [ 306148] INFO – cript.karma.server.KarmaServer – Processing Karma event browserConnected {“id”:”78439233″,”name”:”PhantomJS 2.1.1 (Linux 0.0.0)”,”isAutoCaptured”:true}

    • Oksana Chumak says:

      October 16, 2017

      Please provide the whole file (or even better all contents of log folder in an archive).
      You can upload it here: https://uploads.services.jetbrains.com/. Once uploaded, please let us know its name.

  23. Don G Lazov says:

    October 17, 2017

    File loaded as ideal.log (I accidentally uploaded two, they are the same).

  24. Don Lazov says:

    October 18, 2017

    Done and added a comment. Thank you!

  25. hoeni says:

    November 28, 2019

    Errors with stacktraces are always shown as a link to localhost in the console, like

    at DashboardComponent.dashboardWidgetDefinition (http://localhost:9876/_karma_webpack_/src/app/dashboard/dashboard/dashboard.component.ts:75:33)

    Is there a way to map those links to not open in a browser, but the corresponding file in the IDE?

  26. Casper says:

    January 3, 2020

    Shame there is no change log published.

Latest Tweets

Related posts