When we use !important on a specific less variable, the build fails. We use !important all over the place and I have no idea what makes this one any different.
Setup:
customer1.less
#import "basefile";
#wrapper-height: auto !important;
...
basefile.less
#import 'variables/basefile-variables';
...
basefile-variables.less
#wrapper-height: auto;
...
Error when running gulp-less:
Error in plugin "gulp-less"
Message:
Cannot create property '_index' on string '!important' in file /<redacted>/customer1.less line no. 1
Details:
type: Syntax
filename: /<redacted>/customer1.less
index: NaN
line: 1
column: -1
callLine: NaN
callExtract: undefined
extract: ,#import "basefile";,
lineNumber: 1
fileName: /<redacted>/customer1.less
It could be that your variable #wrapper-height is hyphenated.
Try a var name like #wrapperHeight and see how Gulp handles that.
UPDATED:
Actually, you're trying to import basefile instead of basefile.less - try adding the .less file extension.
Related
I am using eslint to set up my node js project but I keep getting the following warnings:
Now in my .eslint.json I am unable to find a rule/technique to help ignore these new tags and types. I have looked in the following documentation:
https://eslint.org/docs/rules/
I assume that you are also using https://github.com/gajus/eslint-plugin-jsdoc
If so then you have to add this rule to your eslint config file:
"jsdoc/check-tag-names": ["error", { "definedTags": ["consumes", "produces", "route"] }],
and whatever custom tags you also have in your docs...
I recently started using the eslint module to help clean-up some JavaScript files. The following error is being reported when I lint one of my files:
127:17 error Unexpected alias 'me' for 'this' consistent-this
After checking the documentation, I understand the error is being reported because my code is assigning the value of this to a variable named me instead of that.
What is the proper way to configure my project's .eslintrc.json to make it so the following line of code is not reported as an error: var me = this;?
The rule should be like this in your .eslintrc
{
"rules" : {
"consistent-this": ["error", "me"]
}
}
I am using Grunt as my Build Tool and ESLint as my linting tool for an app I am working on. I am also using the Underscore Node package, and have made use of it in my app. Unfortunately, when I run ESLint on my code, it thinks that _ is an undefined variable in the following line:
return _.pluck(objects, nameColumn);
This is the error it is giving me:
78:21 error "_" is not defined no-undef
I would prefer not to disable the no-undef rule for ESLint, and I have tried installing the Underscore plugin, but I am still receiving this error. If anyone else has any ideas for what to try with this, I would be very appreciative!
If there is any further information I can give that would help anyone with helping me get this figured out, just let me know!
The official documentation should give you an idea on how to fix this.
Any reference to an undeclared variable causes a warning, unless the variable is explicitly mentioned in a /*global ...*/ comment, or specified in the globals key in the configuration file.
The easiest fix would be to add
/* global _ */
at the top of your file.
Or better, explicitly specify that the variable is read-only, to disallow overwriting the variable:
/* global _:readonly */
But since you'll have to do that for each new js file, it can get annoying. If you are using underscore often, I'd suggest to add globals to your .eslintrc file, for example:
{
"globals": {
"_": "readonly"
}
}
And save this as .eslintrc in your project root, or optionally in your user home directory. Although some say the latter not recommended, it can sometimes be convenient, but you have to remember that you have it there :)
Explanation of the above rule: "_": "readonly" (used to be "_": false, now deprecated) means that a variable named _ tells eslint that this variable is defined globally and it will not emit any no-undef errors for this variable. As #sebastian pointed out, "readonly" (or false - deprecated) means that the variable can't be overwritten, so the code _ = 'something else' would yield an error no-global-assign. If you were to instead use "_": "writable" (or "_": true - deprecated), this means that the value can be re-assigned and the previously mentioned error will not occur.
But keep in mind that this will only happen if you assign directly to the global variable as I have shown in the example. You can still shadow it and eslint won't say anything. For example, these snippets wouldn't yield the no-global-assign:
const _ = 'haha I broke your _'
or as function argument name, e.g.
function (_) {
console.log(_, 'might not be the _ you were looking for')
}
If you are using jest for testing - in your environment - in eslintrc.json
"env":{
"jest":true
}
My .jscsrc file looks like below
{
"preset": "wikimedia",
"requireSpacesInsideArrayBrackets": null,
"validateIndentation": 4,
"disallowMultipleVarDecl": true,
"disallowSpaceAfterObjectKeys": "ignoreMultiLine",
"disallowSpacesInsideParentheses": { "only": [ "{", "}" ] }
}
But on running jscs over my code, it throws the following error in console
Missing space after opening round bracket at js/app.js :
29 | windowScrollTimeout = null;
30 | if (currentTopOffet < prevTopOffset) {
31 | $('header').removeClass('mobile-hide');
----------------------------------------------------------------^
I also tried setting the value of disallowSpacesInsideParentheses to true but still no change in results. Any idea what I am doing wrong? Or is it that I am trying to solve my problem using wrong rule? Can somebody point me to the right rule set?
Thanks
Checking the source for disallowSpacesInsideParentheses, that rule won't throw the error you're seeing. It seems that your rule is conflicting with the wikimedia presets rule:
"requireSpacesInsideParentheses": "all"
requireSpacesInsideParentheses seems to be the culprit, not any rule you've set, as it's the only rule which will throw that error. To overwrite the preset rule, according to the docs you'll need to set the rule to null in your .jscsrc file.
"requireSpacesInsideParentheses": "null"
I have the following error for my files in tests:
Expected an assignment or function call and instead saw an expression.
It is generated from Chai libraries asserts. How can I turn it off in my .jshintrc file? I run a Gulp task based on it.
Here's how you can silence it inside of a .jshintrc file.
{
...
"expr": true
...
}
Source: http://jshint.com/docs/options/#expr
You can add the following on top of the line that's generating the error :
/*jshint -W030 */
Reference : http://jslinterrors.com/expected-an-assignment-or-function-call