ng test fails Module not found: Error: Can't resolve 'fs' #8357

TKul6 · 2017-11-05T12:41:57Z

Bug Report or Feature Request (mark with an `x`)

- [X] bug report -> please search issues before submitting
- [ ] feature request

Versions.

Angular CLI: 1.5.0
Node: 9.0.0
OS: win32 x64
Angular: 5.0.0
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 1.5.0
@angular-devkit/build-optimizer: 0.0.32
@angular-devkit/core: 0.0.20
@angular-devkit/schematics: 0.0.35
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.8.0
@schematics/angular: 0.1.0
typescript: 2.4.2
webpack: 3.8.1

Repro steps.

ng test

Omits the following error:

ERROR in ./node_modules/fs.realpath/index.js
Module not found: Error: Can't resolve 'fs' in XXXX\node_modules\fs.realpath'
@ ./node_modules/fs.realpath/index.js 8:9-22
@ ./node_modules/jasmine/node_modules/glob/sync.js
@ ./node_modules/jasmine/node_modules/glob/glob.js
@ ./node_modules/jasmine/lib/jasmine.js
@ ./src/client/app/account/login/login.component.spec.ts
@ ./src/client .spec.ts$
@ ./src/client/test.ts

ERROR in ./node_modules/fs.realpath/old.js
Module not found: Error: Can't resolve 'fs' in 'XXXX\node_modules\fs.realpath'
@ ./node_modules/fs.realpath/old.js 24:9-22
@ ./node_modules/fs.realpath/index.js
@ ./node_modules/jasmine/node_modules/glob/sync.js
@ ./node_modules/jasmine/node_modules/glob/glob.js
@ ./node_modules/jasmine/lib/jasmine.js
@ ./src/client/app/account/login/login.component.spec.ts
@ ./src/client .spec.ts$
@ ./src/client/test.ts

ERROR in ./node_modules/jasmine/node_modules/glob/sync.js
Module not found: Error: Can't resolve 'fs' in 'XXXX\node_modules\jasmine\node_modules\glob'
@ ./node_modules/jasmine/node_modules/glob/sync.js 4:9-22
@ ./node_modules/jasmine/node_modules/glob/glob.js
@ ./node_modules/jasmine/lib/jasmine.js
@ ./src/client/app/account/login/login.component.spec.ts
@ ./src/client .spec.ts$
@ ./src/client/test.ts

ERROR in ./node_modules/jasmine/node_modules/glob/glob.js
Module not found: Error: Can't resolve 'fs' inXXXX\node_modules\jasmine\node_modules\glob'
@ ./node_modules/jasmine/node_modules/glob/glob.js 43:9-22
@ ./node_modules/jasmine/lib/jasmine.js
@ ./src/client/app/account/login/login.component.spec.ts
@ ./src/client .spec.ts$
@ ./src/client/test.ts

ERROR in ./node_modules/jasmine/node_modules/jasmine-core/lib/jasmine-core.js
Module not found: Error: Can't resolve 'fs' in 'XXXX\node_modules\jasmine\node_modules\jasmine-core\lib'
@ ./node_modules/jasmine/node_modules/jasmine-core/lib/jasmine-core.js 5:9-22
@ ./node_modules/jasmine/lib/jasmine.js
@ ./src/client/app/account/login/login.component.spec.ts
@ ./src/client .spec.ts$
@ ./src/client/test.ts

Desired functionality.

Run the tests

Mention any other details that might be useful.

It happened when I upgraded from cli 1.47 to 1.5.0.

Jasmine packages:
"jasmine": "^2.8.0",
"jasmine-core": "~2.5.2",
"jasmine-spec-reporter": "~3.2.0"

Karma packages:

"karma": "~1.5.0",
"karma-chrome-launcher": "~2.0.0",
"karma-cli": "~1.0.1",
"karma-coverage-istanbul-reporter": "^1.0.0",
"karma-jasmine": "~1.1.0",
"karma-jasmine-html-reporter": "^0.2.2",
"karma-junit-reporter": "^1.2.0",
"karma-mocha": "^1.3.0",
"karma-phantomjs-launcher": "^1.0.4",

The text was updated successfully, but these errors were encountered:

Scipionh · 2017-11-06T06:33:08Z

Same here

derekaug · 2017-11-07T22:27:14Z

I've spent some time trying to debug this, and no matter what, if I update the @angular/cli package to 1.5.0, this happens to me. I thought maybe it was something in the karma.conf.js and compared my current project's config to a new project's config and it was nearly identical. Even after matching things up as much as possible and disabling some of our plugins this still happens.

Scipionh · 2017-11-27T07:53:52Z

Any news on this issue ?

lammers · 2017-11-27T10:11:24Z

I got the same problem with the jsonpath (npm: "jsonpath": "^1.0.0") library.
ng serve and ng build --prod is working. ng test fails.

ERROR in ./node_modules/jsonpath/lib/grammar.js
Module not found: Error: Can't resolve 'fs' in '/home/m500040/gitrepo/lvm-core-components-client-lib/node_modules/jsonpath/lib'
@ ./node_modules/jsonpath/lib/grammar.js 2:9-22
@ ./node_modules/jsonpath/lib/parser.js
@ ./node_modules/jsonpath/lib/index.js
@ ./node_modules/jsonpath/index.js
@ ./src/app/core/services/json-handler/json-handler.service.ts
@ ./src/app/core/services/json-handler/json-handler.service.spec.ts
@ ./src .spec.ts$
@ ./src/test.ts

adamlubek · 2017-11-27T12:39:55Z

same problem here

lammers · 2017-11-27T12:43:15Z

for my little problem with the jsonpath library a workaround for the issue is using:
import * as jsonPath from 'jsonpath/jsonpath';
instead of
import * as jsonPath from 'jsonpath';
...
jsonPath.query(this._document, path || this.path);

michelre · 2017-11-29T14:37:01Z

Same problem, any news?

Stradivario · 2017-11-30T15:57:50Z

Hello guys same problem here any news ?

phamhaibkit · 2017-12-06T03:45:24Z

same problem,need someone has been resolved

phong-kite · 2017-12-06T07:50:38Z

I had the same error after running ng test that went away after removing import 'jasmine'; from *.spec.ts files.

If the editor is complaining about missing types for jasmine functions, you can fix that by editing tsconfig.spec.json file:

{
  "compilerOptions": {
    "types": [
      "jasmine",
      ...
    ]
  },
 ...
}

RadouaneRoufid · 2017-12-11T10:45:39Z

Same problem here !! Any news ??

kevinkuszyk · 2017-12-12T15:41:16Z

This went away for me after updating to angular@5.1.0 & angular-cli@1.6.0 and following these steps:

remove node_modules
remove package-lock.json
npm cache clean -f

(thanks to @istiti for the comment on #7966).

SearchingSoul · 2017-12-13T05:04:43Z

thanks @kevinkuszyk, 😢 didn't work for me. Still get multiple "Can't resolve 'fs' in...." with angular-cli@1.6.0.

RadouaneRoufid · 2017-12-13T05:48:05Z

I had a "import 'jasmine'" in one of my tests. Removing it solved the problem.

derekaug · 2017-12-15T17:21:13Z

I believe a stray import 'jasmine'; was my issue as well.

SearchingSoul · 2017-12-16T11:33:50Z

I have no "import 'jasmine'" in my tests 😒. tsconfig file is like @phong-kite's comment above.

Perhaps the issue is still open & marked as broken/urgent so probably need to wait..? 🤔

TKul6 · 2017-12-18T17:30:13Z

After upgrading to angular 5.0.1 and the cli to 1.6 And removing the import 'jasmine' everything is working fine.

SearchingSoul · 2017-12-20T06:04:49Z

What worked for me is adding the following to karma.conf.js

webpack: { node: { fs: 'empty', } }

Hope it helps someone.

phamhaibkit · 2017-12-26T07:32:03Z

@SearchingSoul ,I would like to sincerely thank you for your help.It's work for me

Arnaud73 · 2018-01-15T17:58:52Z

Here, with Angular 5.2, Angular CLI 1.6.4, with no reference to import 'jasmine', I had to modify the Karma configuration as described here-before.

Cleaning caches and reinstalling NPM modules did not help.

xmeng1 · 2018-02-05T14:32:55Z

I think this is the issue of Webpack, see this issue webpack-contrib/css-loader#447 , and @SearchingSoul 's configuration solves it.

DenysVuika · 2018-02-21T16:35:28Z

I have suddenly started getting the same issue today after removing lock files, with CLI 1.6.6. The only thing that helped me is the trick with "karma.conf.js" mentioned above:

webpack: { node: { fs: 'empty', } }

TKul6 · 2018-02-25T21:35:20Z

I had the same error today AGAIN.
The root cause was in the beforeEach() hook when I created the testing module without providing all the necessary mocks.

Now, I get the code shouldn't wok in this scenario, but it would be nice to have more indicative message.

ravivit9 · 2018-03-08T11:30:47Z

@SearchingSoul the webpack: { node: { fs: 'empty', } } sort of get rid of the fs error but when I run ng test the chrome test window simply not starting.
08 03 2018 11:28:26.966:INFO [launcher]: Launching browser Chrome with unlimited concurrency
08 03 2018 11:28:26.981:INFO [launcher]: Starting browser Chrome 08 03 2018 11:29:26.985:WARN [launcher]: Chrome have not captured in 60000 ms, killing.
08 03 2018 11:29:27.092:INFO [launcher]: Trying to start Chrome again (1/2).
08 03 2018 11:30:27.090:WARN [launcher]: Chrome have not captured in 60000 ms, killing.
08 03 2018 11:30:27.275:INFO [launcher]: Trying to start Chrome again (2/2).
08 03 2018 11:31:27.278:WARN [launcher]: Chrome have not captured in 60000 ms, killing.
08 03 2018 11:31:27.374:ERROR [launcher]: Chrome failed 2 times (timeout). Giving up.

And returns to command prompt.

And the ng test will keep trying to start again and again endlessly. Any thoughts?

BTW, I am not using webpage but angular-cli.

SearchingSoul · 2018-03-21T14:01:02Z

@ravivit9 , its only supposed to take care of the 'fs' error. Other errors could be due to other reasons. Yours looks like something to do with your karma 😬.

havart · 2018-04-10T08:40:56Z

Hi All,
I had the same error.
The error was that I imported the wrong HttpClient (import { HttpClient } from 'selenium-webdriver/http';) module into the component.

splincode · 2018-08-02T10:12:46Z

Can't resolve 'child_process' it too have problem

ERROR in ./packages/cli/node_modules/external-editor/main/index.js
Module not found: Error: Can't resolve 'child_process' in '/Users/splincode/Documents/Develop/store/packages/cli/node_modules/external-editor/main'
 @ ./packages/cli/node_modules/external-editor/main/index.js 17:14-38 19:10-34
 @ ./packages/cli/node_modules/inquirer/lib/prompts/editor.js
 @ ./packages/cli/node_modules/inquirer/lib/inquirer.js
 @ ./packages/cli/node_modules/node-plop/lib/node-plop.js
 @ ./packages/cli/node_modules/node-plop/lib/index.js
 @ ./packages/cli/tests/cli.spec.ts
 @ ./packages sync \.spec\.ts$
 @ ./test.ts

I set

webpack: {
      node: {
        fs: 'empty',
        child_process: 'empty',
        readline: 'empty'
      }
    },

output

02 08 2018 13:10:38.024:INFO [Chrome 68.0.3440 (Mac OS X 10.13.6)]: Connected on socket vvF5Oc_mUnJw0zmgAAAA with id 94325210
Chrome 68.0.3440 (Mac OS X 10.13.6) ERROR
  {
    "message": "Uncaught Error: process.binding is not supported\nat http://localhost:9876/_karma_webpack_/vendor.js:82248:5\n\nError: process.binding is not supported\n    at Object.push../node_modules/process/browser.js.process.binding (http://localhost:9876/_karma_webpack_/vendor.js:82248:11)\n    at Object.<anonymous> (http://localhost:9876/_karma_webpack_/vendor.js:189191:20)\n    at Object../packages/cli/node_modules/tmp/lib/tmp.js (http://localhost:9876/_karma_webpack_/vendor.js:189788:30)\n    at __webpack_require__ (http://localhost:9876/_karma_webpack_/main.js:77:30)\n    at Object.<anonymous> (http://localhost:9876/_karma_webpack_/vendor.js:134661:10)\n    at Object.<anonymous> (http://localhost:9876/_karma_webpack_/vendor.js:134875:4)\n    at Object../packages/cli/node_modules/external-editor/main/index.js (http://localhost:9876/_karma_webpack_/vendor.js:134877:30)\n    at __webpack_require__ (http://localhost:9876/_karma_webpack_/main.js:77:30)\n    at Object../packages/cli/node_modules/inquirer/lib/prompts/editor.js (http://localhost:9876/_karma_webpack_/vendor.js:149457:22)\n    at __webpack_require__ (http://localhost:9876/_karma_webpack_/main.js:77:30)",
    "str": "Uncaught Error: process.binding is not supported\nat http://localhost:9876/_karma_webpack_/vendor.js:82248:5\n\nError: process.binding is not supported\n    at Object.push../node_modules/process/browser.js.process.binding (http://localhost:9876/_karma_webpack_/vendor.js:82248:11)\n    at Object.<anonymous> (http://localhost:9876/_karma_webpack_/vendor.js:189191:20)\n    at Object../packages/cli/node_modules/tmp/lib/tmp.js (http://localhost:9876/_karma_webpack_/vendor.js:189788:30)\n    at __webpack_require__ (http://localhost:9876/_karma_webpack_/main.js:77:30)\n    at Object.<anonymous> (http://localhost:9876/_karma_webpack_/vendor.js:134661:10)\n    at Object.<anonymous> (http://localhost:9876/_karma_webpack_/vendor.js:134875:4)\n    at Object../packages/cli/node_modules/external-editor/main/index.js (http://localhost:9876/_karma_webpack_/vendor.js:134877:30)\n    at __webpack_require__ (http://localhost:9876/_karma_webpack_/main.js:77:30)\n    at Object../packages/cli/node_modules/inquirer/lib/prompts/editor.js (http://localhost:9876/_karma_webpack_/vendor.js:149457:22)\n    at __webpack_require__ (http://localhost:9876/_karma_webpack_/main.js:77:30)"
  }
Chrome 68.0.3440 (Mac OS X 10.13.6) ERROR
  {
    "message": "Uncaught Error: process.binding is not supported\nat http://localhost:9876/_karma_webpack_/vendor.js:82248:5\n\nError: process.binding is not supported\n    at Object.push../node_modules/process/browser.js.process.binding (http://localhost:9876/_karma_webpack_/vendor.js:82248:11)\n    at Object.<anonymous> (http://localhost:9876/_karma_webpack_/vendor.js:189191:20)\n    at Object../packages/cli/node_modules/tmp/lib/tmp.js (http://localhost:9876/_karma_webpack_/vendor.js:189788:30)\n    at __webpack_require__ (http://localhost:9876/_karma_webpack_/main.js:77:30)\n    at Object.<anonymous> (http://localhost:9876/_karma_webpack_/vendor.js:134661:10)\n    at Object.<anonymous> (http://localhost:9876/_karma_webpack_/vendor.js:134875:4)\n    at Object../packages/cli/node_modules/external-editor/main/index.js (http://localhost:9876/_karma_webpack_/vendor.js:134877:30)\n    at __webpack_require__ (http://localhost:9876/_karma_webpack_/main.js:77:30)\n    at Object../packages/cli/node_modules/inquirer/lib/prompts/editor.js (http://localhost:9876/_karma_webpack_/vendor.js:149457:22)\n    at __webpack_require__ (http://localhost:9876/_karma_webpack_/main.js:77:30)",
    "str": "Uncaught Error: process.binding is not supported\nat http://localhost:9876/_karma_webpack_/vendor.js:82248:5\n\nError: process.binding is not supported\n    at Object.push../node_modules/process/browser.js.process.binding (http://localhost:9876/_karma_webpack_/vendor.js:82248:11)\n    at Object.<anonymous> (http://localhost:9876/_karma_webpack_/vendor.js:189191:20)\n    at Object../packages/cli/node_modules/tmp/lib/tmp.js (http://localhost:9876/_karma_webpack_/vendor.js:189788:30)\n    at __webpack_require__ (http://localhost:9876/_karma_webpack_/main.js:77:30)\n    at Object.<anonymous> (http://localhost:9876/_karma_webpack_/vendor.js:134661:10)\n    at Object.<anonymous> (http://localhost:9876/_karma_webpack_/vendor.js:134875:4)\n    at Object../packages/cli/node_modules/external-editor/main/index.js (http://localhost:9876/_karma_webpack_/vendor.js:134877:30)\n    at __webpack_require__ (http://localhost:9876/_karma_webpack_/main.js:77:30)\n    at Object../packages/cli/node_modules/inquirer/lib/prompts/editor.js (http://localhost:9876/_karma_webpack_/vendor.js:149457:22)\n    at __webpack_require__ (http://localhost:9876/_karma_webpack_/main.js:77:30)"
  }

Chrome 68.0.3440 (Mac OS X 10.13.6) ERROR
  {
    "message": "Uncaught Error: process.binding is not supported\nat http://localhost:9876/_karma_webpack_/vendor.js:82248:5\n\nError: process.binding is not supported\n    at Object.push../node_modules/process/browser.js.process.binding (http://localhost:9876/_karma_webpack_/vendor.js:82248:11)\n    at Object.<anonymous> (http://localhost:9876/_karma_webpack_/vendor.js:189191:20)\n    at Object../packages/cli/node_modules/tmp/lib/tmp.js (http://localhost:9876/_karma_webpack_/vendor.js:189788:30)\n    at __webpack_require__ (http://localhost:9876/_karma_webpack_/main.js:77:30)\n    at Object.<anonymous> (http://localhost:9876/_karma_webpack_/vendor.js:134661:10)\n    at Object.<anonymous> (http://localhost:9876/_karma_webpack_/vendor.js:134875:4)\n    at Object../packages/cli/node_modules/external-editor/main/index.js (http://localhost:9876/_karma_webpack_/vendor.js:134877:30)\n    at __webpack_require__ (http://localhost:9876/_karma_webpack_/main.js:77:30)\n    at Object../packages/cli/node_modules/inquirer/lib/prompts/editor.js (http://localhost:9876/_karma_webpack_/vendor.js:149457:22)\n    at __webpack_require__ (http://localhost:9876/_karma_webpack_/main.js:77:30)",
    "str": "Uncaught Error: process.binding is not supported\nat http://localhost:9876/_karma_webpack_/vendor.js:82248:5\n\nError: process.binding is not supported\n    at Object.push../node_modules/process/browser.js.process.binding (http://localhost:9876/_karma_webpack_/vendor.js:82248:11)\n    at Object.<anonymous> (http://localhost:9876/_karma_webpack_/vendor.js:189191:20)\n    at Object../packages/cli/node_modules/tmp/lib/tmp.js (http://localhost:9876/_karma_webpack_/vendor.js:189788:30)\n    at __webpack_require__ (http://localhost:9876/_karma_webpack_/main.js:77:30)\n    at Object.<anonymous> (http://localhost:9876/_karma_webpack_/vendor.js:134661:10)\n    at Object.<anonymous> (http://localhost:9876/_karma_webpack_/vendor.js:134875:4)\n    at Object../packages/cli/node_modules/external-editor/main/index.js (http://localhost:9876/_karma_webpack_/vendor.js:134877:30)\n    at __webpack_require__ (http://localhost:9876/_karma_webpack_/main.js:77:30)\n    at Object../packages/cli/node_modules/inquirer/lib/prompts/editor.js (http://localhost:9876/_karma_webpack_/vendor.js:149457:22)\n    at __webpack_require__ (http://localhost:9876/_karma_webpack_/main.js:77:30)"
  }

02 08 2018 13:11:04.226:WARN [Chrome 68.0.3440 (Mac OS X 10.13.6)]: Disconnected (1 times)
Chrome 68.0.3440 (Mac OS X 10.13.6) ERROR
  Disconnected
Chrome 68.0.3440 (Mac OS X 10.13.6) ERROR
  Disconnected

Chrome 68.0.3440 (Mac OS X 10.13.6) ERROR
  Disconnected

kblestarge · 2018-10-17T16:19:38Z

@havart pointed me in the right direction. My errors were caused by importing the wrong EventEmitter in a component:
changed
import { EventEmitter } from 'selenium-webdriver';
to
import { EventEmitter } from '@angular/core';
and the problem is fixed :)

StanislavChankov · 2018-11-29T14:37:32Z

@havart pointed me in the right direction. My errors were caused by importing the wrong EventEmitter in a component:
changed
import { EventEmitter } from 'selenium-webdriver';
to
import { EventEmitter } from '@angular/core';
and the problem is fixed :)

This fixes the following errors:
For each node module
ERROR in ./node_modules/...

alan-agius4 · 2018-12-06T16:32:30Z

Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version.

If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.

Pradhan10 · 2019-04-08T08:56:31Z

I had the same error after running ng test that went away after removing import 'jasmine'; from *.spec.ts files.

If the editor is complaining about missing types for jasmine functions, you can fix that by editing tsconfig.spec.json file:
{
  "compilerOptions": {
    "types": [
      "jasmine",
      ...
    ]
  },
 ...
}

This worked for me

angular-automatic-lock-bot · 2019-09-09T11:41:00Z

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}

kamal2311 mentioned this issue Nov 7, 2017

Can we remove dependency on module fs? tapmodo/node-ldap-filters#3

Open

Brocco assigned hansl Nov 13, 2017

Brocco added P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful severity3: broken labels Nov 13, 2017

lammers mentioned this issue Nov 27, 2017

Using jsonpath in a Angular 5 Karma Unit Test dchester/jsonpath#81

Closed

xmeng1 mentioned this issue Feb 5, 2018

fs issue with karma, maybe need to update the document darekf77/ng2-logger#30

Closed

hansl removed their assignment Feb 6, 2018

splincode mentioned this issue Aug 2, 2018

feat(cli): add @ngxs/cli for generate store ngxs/store#520

Merged

3 tasks

alan-agius4 closed this as completed Dec 6, 2018

angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019

ng test fails Module not found: Error: Can't resolve 'fs' #8357

ng test fails Module not found: Error: Can't resolve 'fs' #8357

TKul6 commented Nov 5, 2017

Scipionh commented Nov 6, 2017

derekaug commented Nov 7, 2017

Scipionh commented Nov 27, 2017

lammers commented Nov 27, 2017

adamlubek commented Nov 27, 2017

lammers commented Nov 27, 2017

michelre commented Nov 29, 2017

Stradivario commented Nov 30, 2017

phamhaibkit commented Dec 6, 2017

phong-kite commented Dec 6, 2017 •

edited

RadouaneRoufid commented Dec 11, 2017

kevinkuszyk commented Dec 12, 2017

SearchingSoul commented Dec 13, 2017

RadouaneRoufid commented Dec 13, 2017

derekaug commented Dec 15, 2017

SearchingSoul commented Dec 16, 2017

TKul6 commented Dec 18, 2017

SearchingSoul commented Dec 20, 2017

phamhaibkit commented Dec 26, 2017

Arnaud73 commented Jan 15, 2018

xmeng1 commented Feb 5, 2018

DenysVuika commented Feb 21, 2018

TKul6 commented Feb 25, 2018

ravivit9 commented Mar 8, 2018 •

edited

SearchingSoul commented Mar 21, 2018

havart commented Apr 10, 2018

splincode commented Aug 2, 2018 •

edited

kblestarge commented Oct 17, 2018 •

edited

StanislavChankov commented Nov 29, 2018

alan-agius4 commented Dec 6, 2018

Pradhan10 commented Apr 8, 2019

angular-automatic-lock-bot bot commented Sep 9, 2019

ng test fails Module not found: Error: Can't resolve 'fs' #8357

ng test fails Module not found: Error: Can't resolve 'fs' #8357

Comments

TKul6 commented Nov 5, 2017

Bug Report or Feature Request (mark with an x)

Versions.

Repro steps.

Desired functionality.

Mention any other details that might be useful.

Scipionh commented Nov 6, 2017

derekaug commented Nov 7, 2017

Scipionh commented Nov 27, 2017

lammers commented Nov 27, 2017

adamlubek commented Nov 27, 2017

lammers commented Nov 27, 2017

michelre commented Nov 29, 2017

Stradivario commented Nov 30, 2017

phamhaibkit commented Dec 6, 2017

phong-kite commented Dec 6, 2017 • edited

RadouaneRoufid commented Dec 11, 2017

kevinkuszyk commented Dec 12, 2017

SearchingSoul commented Dec 13, 2017

RadouaneRoufid commented Dec 13, 2017

derekaug commented Dec 15, 2017

SearchingSoul commented Dec 16, 2017

TKul6 commented Dec 18, 2017

SearchingSoul commented Dec 20, 2017

phamhaibkit commented Dec 26, 2017

Arnaud73 commented Jan 15, 2018

xmeng1 commented Feb 5, 2018

DenysVuika commented Feb 21, 2018

TKul6 commented Feb 25, 2018

ravivit9 commented Mar 8, 2018 • edited

SearchingSoul commented Mar 21, 2018

havart commented Apr 10, 2018

splincode commented Aug 2, 2018 • edited

kblestarge commented Oct 17, 2018 • edited

StanislavChankov commented Nov 29, 2018

alan-agius4 commented Dec 6, 2018

Pradhan10 commented Apr 8, 2019

angular-automatic-lock-bot bot commented Sep 9, 2019

Bug Report or Feature Request (mark with an `x`)

phong-kite commented Dec 6, 2017 •

edited

ravivit9 commented Mar 8, 2018 •

edited

splincode commented Aug 2, 2018 •

edited

kblestarge commented Oct 17, 2018 •

edited