There are 2 option for JavaScript validation in Eclipse:
- JSDT
- JSHint (default since Nodeclipse 0.7)
As configration is stored per project, copy .* settings files from project created with 0.7 or re-configure it manually (just compare .* files with newly created project). Then put .jshintrc file like https://github.com/Nodeclipse/nodeclipse-1/blob/master/org.nodeclipse.ui/templates/.jshintrc
Try to check JSHint options, if it is possible.
Note that with JSHint usage, ~~this question becomes general JSHint question (not Eclipse or Nodeclipse related).~~
UPDATE:
.project
content since 0.7 :
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>ProjectName</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
<buildCommand>
<name>com.eclipsesource.jshint.ui.builder</name>
<arguments>
</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>org.nodeclipse.ui.NodeNature</nature>
<nature>org.eclipse.wst.jsdt.core.jsNature</nature>
</natures>
</projectDescription>
As @Jess discovered this was error shown by JSDT, not JSHInt,
so removing <nature>org.eclipse.wst.jsdt.core.jsNature</nature>
will stop JSDT from displaying it (even with JavaScript semantic validation already turned off since 0.7)
UPDATE 3:
Drawback of <nature>org.eclipse.wst.jsdt.core.jsNature</nature>
removed will be that code assist and click-though to definition will not work (It actually works in rare cases when JSDocs are defined e.g. http://www.nodeclipse.org/nodejs/javascript/sources/books/2013/10/22/JSDT-require-JSDoc.html or within 1 .js file)
Even click-through to definition