Pretty nice company. It's a really amazing place.
I'm gonna do JS dev full time now :)
When it's not there, everything works as-expected, and when it is, VSCode pops up a little error:
def.split is not a function, and the linting stops.
It looks like the same error is happening in Standard: standard/standard#1047
That also fixed another issue I was having with "envs".
Might I suggest making it clearer in the documentation that the formatting for some of the config is the same as ESLint ("rules: {}"), and some is not ("envs": [])?
Or, even better, make all of the config match the ESLint format.
As-is, I can't define my globals to be rewriteable or not, since they can't be true/false.
Maybe there's a way to change this that I don't know about
prettier/prettier#4845
Hi all. In meteor it's common to do import './some-template.html'but this causes an Imported module should be assigned import/no-unassigned-import error.
I've already got a rule override for this rule to allow meteor packages (with only side-effects) to work:
"xo": {
"prettier": true,
"semicolon": false,
"space": 2,
"settings": {
"import/resolver": "meteor"
},
"rules": {
"import/no-absolute-path": 0,
"import/no-unassigned-import": ["error", {
"allow": ["meteor/*:*"] // this allows: `import 'meteor/meteorhacks:unblock'`
}]
}
}I was hoping to simply add *.html to the allow section but it still throws the same error. Any ideas?
Derp. I got the glob wrong. It should be
"**/*.html". I put together a quick overview of this and some other helpful XO settings for meteor here: https://github.com/xojs/xo/issues/262#issuecomment-406865385. If you guys know of any other meteor specific settings please let me know. Cheers!
// @pvdlg
Here a part of my package.json
"devDependencies": {
"eslint": "^5.3.0",
"eslint-config-xo": "^0.24.1",
"eslint-config-xo-typescript": "^0.1.0",
"eslint-plugin-typescript": "^0.12.0",
"tslint": "~5.9.1",
"typescript": "^2.9.2",
"typescript-eslint-parser": "^17.0.1",
"xo": "^0.21.1"
},
"xo": {
"extends": "xo-typescript",
"space": 2,
"env": [
"browser",
"node"
]
}
In Atom? Or when you run
xo in the root of the repo?
Ah ok. I misunderstood your question. Yes, use you use
/* eslint-env jest */ at the top of the file or use the overrides feature to only target test files: https://github.com/xojs/xo#config-overrides
I am in trapped in some kind of configuration loop. I have people in my node.js project, that are non developers, but like to code. So I thought I give xo a try. Now How can I use a linting enabled Vscode based on let's say xo rules that can later be adjusted with .eslintrc - atm I am pretty indifferent what rules to use, Important is that my fellows use a linter and something that fixes/make the code prettier - therefore I am trying to get eslint plugin in vscode running with prettier, that handle corrections on save. But prettier or eslint wouldn't use the xo rules with zero config
Or maybe xo is not what I am looking for.
@kivi If you use Prettier, you need to enable the
prettier XO option: https://github.com/xojs/xo#prettier
You don't adjust the rules with
.eslintrc, but rather in the xo.rules config in package.json.
You can also use shareable ESLint config if you need to share the rule customizations. See the
extends option in the XO docs.
@sindresorhus
@itaisteinherz No, XO config can only be defined in package.json. Why do you need to define it outside package.json?
If you work in a team there might be other linters cleaning the code. Most probably all developers (and none developers) use an editor, which is able to workd with .editorconfig. So why not define the linting params in .editorconfig?