Warning: Path must be a string. Received null Use --force to continue #2922

xtianus79 · 2016-05-03T14:56:06Z

The path seems correct and I even went root to root and it is still giving this error.

when I run -v it is

outputing this:

options: force=false, reporterOutput=null, jshintrc="client/.jshintrc", reporter="/theAppHere/node_modules/jshint-stylish/stylish.js"
Warning: Path must be a string. Received null Use --force to continue.

Update:

Just to add... this is happening since upgrading from 5.11 to 6.0

MrSwitch · 2016-05-09T11:36:40Z

What version of jshint are you using? I received this error when using v2.5, but not the latest, v2.9.2.

FYI: i was using it through grunt-contrib-jshint (and updated that to resolve this error)

xtianus79 · 2016-05-09T21:22:23Z

@MrSwitch my jshint is jshint v2.9.2

jeffpeck-intellify · 2016-05-13T20:10:32Z

I am having the same issue, using jshint v2.9.2

jeffpeck-intellify · 2016-05-15T03:07:47Z

I have found the issue to be when the reporterOutput option is set to null. If you change that option to refer to an empty string, jshint will work as expected:

options: {
      jshintrc: '<%= baseDir %>/.jshintrc',
      reporterOutput: "",
      ...

ghost · 2016-05-16T16:46:30Z

Explicitly setting "reporterOutput" fixed the warning in travis-ci build in my case. Thanks.

shershen08 · 2016-05-19T09:50:45Z

"options": { "jshintrc": "<%= baseDir %>.jshintrc",
worked for me, mind no slash "/" after <%= baseDir %>

jugglinmike · 2016-05-29T18:21:57Z

This looks to me like an issue with the Grunt plugin, not JSHint itself. Can anyone who has responded so far demonstrate this problem using JSHint without the plugin?

coryasilva · 2016-06-24T14:50:01Z

I do not have this problem with the latest gulp packages (as of 2016-06-18), but opened an older project today with grunt and observed this issue. Thanks to @jeffpeck-intellify for the work around; you saved me some time today!

Thanks to jshint/jshint#2922 (comment)

Do not upgrade jshint because of false negative "unused variable" errors.

…#2922

Fixes failing `grunt jshint` task: Running "jshint:lib" (jshint) task Verifying property jshint.lib exists in config...OK Files: lib/esl/Connection.js, lib/esl/Event.js, lib/esl/Parser.js, lib/esl/Server.js, lib/esl/esl.js, lib/index.js Options: force=false, reporterOutput=null, jshintrc=".jshintrc" Warning: Path must be a string. Received null Use --force to continue. Aborted due to warnings. Likely fixed by gruntjs/grunt-contrib-jshint@a0cd3db which was needed due to a newer jshint version, see jshint/jshint#2922 After the upgrade, have to disable a camelcase warning (W106) that cannot be fixed since it is part of the interface. This also silences some deprecation warnings in newer node versions.

Lekensteyn · 2016-08-02T17:29:21Z

@jugglinmike If I may guess, it is fixed in grunt-contrib-jshint via gruntjs/grunt-contrib-jshint@a0cd3db.

…around at jshint/jshint#2922 (comment)

Was throwing "Warning: Path must be a string. Received null Use --force to continue." See jshint/jshint#2922 Also move shared jshintrc into root options.

jarimbi · 2016-10-07T18:13:25Z

Thanks for much for the tip of 'reporterOutput: "",'
I had no clue what was going wrong!

An issue was filed on jshint's github about this jshint/jshint#2922. The solution seems to be to explicitly define a reporterOutput option with a value of empty string. After making this change, grunt builds ran flawlessly.

Fix null error in jshint grunt plugin An issue was filed on jshint's github about this jshint/jshint#2922. The solution seems to be to explicitly define a reporterOutput option with a value of empty string. After making this change, grunt builds ran flawlessly.

…ix null path error

After a fresh install I got: ``` $ node_modules/.bin/grunt javascripts Running "javascripts" task Running "concat:dist" (concat) task File grappelli/static/grappelli/js/grappelli.min.js created. Running "jshint:afterconcat" (jshint) task Warning: Path must be a string. Received null Use --force to continue. Aborted due to warnings. ``` This is a known issue, with this fix: jshint/jshint#2922 (comment)

jshint/jshint#2922 (comment)

flyher · 2017-06-28T08:50:09Z

After i update the grunt-contrib-jshint from version 0.9 to 1.0, the bug fixed.
my node version: 6.0 and i test it in node version 5.0.
This table is my record.

node version	grunt-contrib-jshint	grunt dev	error code
4.4.3	~0.9.2	success
6.11	~0.9.2	build failed	Warning: Path must be a string. Received null Use --force to continue
6.11	~1.1.0	success

jugglinmike · 2017-07-08T16:27:00Z

At this point, it seems fairly conclusive that this problem is with the
grunt-contrib-jshint module. Happily, this has been resolved in recent
versions, and for those who can't upgrade just yet, the comments above have
some ideas for workarounds. Thanks, all.

Without this fix, I received "Warning: Path must be a string", see jshint/jshint#2922

Updating the node version broke jshint for some reason, but fortunately not very badly. Found the relevant fix here: jshint/jshint#2922 (comment) With jshint working again, I went back and fixed some of the syntax errors I'd introduced.

Without this fix, I received "Warning: Path must be a string", see jshint/jshint#2922

Updating the node version broke jshint for some reason, but fortunately not very badly. Found the relevant fix here: jshint/jshint#2922 (comment) With jshint working again, I went back and fixed some of the syntax errors I'd introduced.

See jshint/jshint#2922

See jshint/jshint#2922 > Running "jshint:code" (jshint) task > Warning: Path must be a string. Received null Use --force to continue. > > Aborted due to warnings.

jshint/jshint#2922

* feat(travis): travis * node ^6 package.json * chrome launcher * Gruntfile: reporterOutpu: '' jshint/jshint#2922 * jshint fixes * karma -> Chrome * add in chrome start stuff * add empty test * test/jshintrc * use strict lulz * test/jshintrc globals * switch to non-pro key * maybe this key will work?? * third times a charm? * travis login --org * skip cleanup * bump angular-ui-router: ~0.3.2

jshint/jshint#2922

Fixes failing `grunt jshint` task: Running "jshint:lib" (jshint) task Verifying property jshint.lib exists in config...OK Files: lib/esl/Connection.js, lib/esl/Event.js, lib/esl/Parser.js, lib/esl/Server.js, lib/esl/esl.js, lib/index.js Options: force=false, reporterOutput=null, jshintrc=".jshintrc" Warning: Path must be a string. Received null Use --force to continue. Aborted due to warnings. Likely fixed by gruntjs/grunt-contrib-jshint@a0cd3db which was needed due to a newer jshint version, see jshint/jshint#2922 After the upgrade, have to disable a camelcase warning (W106) that cannot be fixed since it is part of the interface. This also silences some deprecation warnings in newer node versions.

…nt/issues/2922.

jeffpeck-intellify mentioned this issue May 15, 2016

Latest release (0.11.0) fails when reporterOutput is set to the default value (null) gruntjs/grunt-contrib-jshint#256

Closed

ghost pushed a commit to AhmedMRaihan/rokeya-keyboard-layout that referenced this issue May 16, 2016

Trying to fix jsHint warning as per jshint/jshint#2922

2cf05ef

jugglinmike added the Needs Information label May 29, 2016

marcandre added a commit to noelboss/featherlight that referenced this issue Jun 27, 2016

Fix build issue.

9dbf4e8

Thanks to jshint/jshint#2922 (comment)

timdream added a commit to timdream/wordcloud2.js that referenced this issue Jul 12, 2016

Workaround jshint/jshint#2922 so the old jshint could work on Node v6.x

9573954

Do not upgrade jshint because of false negative "unused variable" errors.

kalahari added a commit to kalahari/koalab that referenced this issue Jul 27, 2016

attempt to disable color codes in build output, fix for jshint/jshint…

b13cab6

…#2922

jonathanstegall added a commit to MinnPost/minnpost-elections-dashboard that referenced this issue Aug 4, 2016

add empty string for reporterOutput option on jshint. found this work…

8021c43

…around at jshint/jshint#2922 (comment)

mglaman added a commit to mglaman/dreditor that referenced this issue Aug 23, 2016

Fixup jshint in Gruntfile

9564a4e

Was throwing "Warning: Path must be a string. Received null Use --force to continue." See jshint/jshint#2922 Also move shared jshintrc into root options.

mglaman mentioned this issue Aug 23, 2016

Fixup jshint in Gruntfile dreditor/dreditor#1

Closed

bpasero mentioned this issue Sep 19, 2016

Error: Path must be a string. Received null due to some plugin microsoft/vscode#12229

Closed

markshust mentioned this issue Sep 26, 2016

Fix jshint errors on grunt build leongersen/noUiSlider#697

Merged

gargi mentioned this issue Oct 6, 2016

Add Travis CI support frankcash/HackerQueue#49

Merged

copperwall mentioned this issue Oct 23, 2016

Fix null error in jshint grunt plugin iFixit/pulldasher#53

Merged

LordPachelbel added a commit to LordPachelbel/grunt-init-gruntfile that referenced this issue Oct 26, 2016

Added reporterOutput to jshint options as per jshint/jshint#2922 to f…

24e4219

…ix null path error

LordPachelbel mentioned this issue Oct 26, 2016

Add reporterOutput to jshint options gruntjs/grunt-init-gruntfile#12

Open

nabil-boag mentioned this issue Mar 12, 2017

Deduplicate scenario data nabil-boag/angular-multimocks#59

Merged

dennisvg111 mentioned this issue Mar 20, 2017

Update dist build, fixed gruntfile to allow other package names dsmorse/gridster.js#88

Merged

fians pushed a commit to fians/Waves that referenced this issue Mar 20, 2017

Fix jshint jshint/jshint#2922 #164

6936eab

ghost pushed a commit to nsidc/search-interface that referenced this issue Mar 28, 2017

Work around weird jshint error

b3e0f90

jshint/jshint#2922 (comment)

snypelife mentioned this issue Apr 1, 2017

Feature/dark mode support keithclark/gadebugger#41

Merged

mguimard added a commit to docdoku/docdoku-plm that referenced this issue Apr 27, 2017

Fix grunt-jshint bug on newer versions (jshint/jshint#2922)

86a6ccf

matthewberryman mentioned this issue Apr 29, 2017

error running grunt in static branch smart-facility/petajakarta-web#127

Closed

jugglinmike closed this as completed Jul 8, 2017

jugglinmike added cannot reproduce or not an issue and removed Needs Information labels Jul 8, 2017

caseylitton mentioned this issue Jul 20, 2017

Change Gruntfile paths to correct ones Stanford-Online/xblock-qualtrics-survey#6

Merged

michelefenu mentioned this issue Aug 25, 2017

Fix for #329: Loop, keypress and item 1 bugs out sachinchoolur/lightslider#349

Closed

sualko added a commit to sualko/otr that referenced this issue Sep 19, 2017

fix grunt error

eea0d11

Without this fix, I received "Warning: Path must be a string", see jshint/jshint#2922

arlolra pushed a commit to arlolra/otr that referenced this issue Oct 10, 2017

fix grunt error

25bfc26

Without this fix, I received "Warning: Path must be a string", see jshint/jshint#2922

mtrias added a commit to VividCortex/grunt-circleci that referenced this issue Oct 21, 2017

[yarn] - upgrade jshint which was failing due to an apparently known bug

bd22a82

See jshint/jshint#2922

timkrins mentioned this issue Dec 13, 2017

Fix "Warning: Path must be a string." timmywil/generator-threejs#7

Open

anttikuuskoski added a commit to anttikuuskoski/select2 that referenced this issue Feb 23, 2018

Fix jshint error

b967188

See jshint/jshint#2922 > Running "jshint:code" (jshint) task > Warning: Path must be a string. Received null Use --force to continue. > > Aborted due to warnings.

davious added a commit to NCARB/StyleGuide that referenced this issue Apr 30, 2018

Gruntfile: reporterOutpu: ''

69381a8

jshint/jshint#2922

koenweyn added a commit to acsl/select2 that referenced this issue May 16, 2018

Fix for grunt-contrib-jshint

b44356d

jshint/jshint#2922

tophstar mentioned this issue Jan 14, 2020

jshint preventing grunt build tophstar/lib-ng-terminal#2

Open

bot-linagora mentioned this issue Jun 11, 2022

[Snyk] Upgrade node-waves from 0.7.5 to 0.7.6 linagora/linshare-ui-user#18

Closed

dmore pushed a commit to dmore/SkylinkJS that referenced this issue Aug 7, 2023

ESS-498 Fixes for jshint reportOutput bug. See github.com/jshint/jshi…

e7387f9

…nt/issues/2922.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Warning: Path must be a string. Received null Use --force to continue #2922

Warning: Path must be a string. Received null Use --force to continue #2922

xtianus79 commented May 3, 2016 •

edited

MrSwitch commented May 9, 2016

xtianus79 commented May 9, 2016

jeffpeck-intellify commented May 13, 2016

jeffpeck-intellify commented May 15, 2016

ghost commented May 16, 2016

shershen08 commented May 19, 2016

jugglinmike commented May 29, 2016

coryasilva commented Jun 24, 2016 •

edited

Lekensteyn commented Aug 2, 2016

jarimbi commented Oct 7, 2016

flyher commented Jun 28, 2017 •

edited

jugglinmike commented Jul 8, 2017

Warning: Path must be a string. Received null Use --force to continue #2922

Warning: Path must be a string. Received null Use --force to continue #2922

Comments

xtianus79 commented May 3, 2016 • edited

MrSwitch commented May 9, 2016

xtianus79 commented May 9, 2016

jeffpeck-intellify commented May 13, 2016

jeffpeck-intellify commented May 15, 2016

ghost commented May 16, 2016

shershen08 commented May 19, 2016

jugglinmike commented May 29, 2016

coryasilva commented Jun 24, 2016 • edited

Lekensteyn commented Aug 2, 2016

jarimbi commented Oct 7, 2016

flyher commented Jun 28, 2017 • edited

jugglinmike commented Jul 8, 2017

xtianus79 commented May 3, 2016 •

edited

coryasilva commented Jun 24, 2016 •

edited

flyher commented Jun 28, 2017 •

edited