Closed hafley66 closed 7 years ago
It looks like for some reason your Atom install isn't properly transcoding the files into a usable format, investigating...
It is much appreciated. For now I'm going to run eslint-watch from command line
Downgraded to 8.0.0 and it worked, will try again another time.
Can you try this?
~/.atom/compile-cache/package-transpile/linter-eslint
folderapm uninstall linter-eslint; apm install linter-eslint
(just in case)For what it's worth, @Arcanemagus & @hafley66, it’s possible the issue is being caused by a .babelrc
file somewhere up the file tree messing with transpilation during install, as noted in https://github.com/AtomLinter/linter-eslint/pull/890. For me, that’s in ~
. At various points, Atom/linter-eslint
were not finding the preset env
relative to ~
or that regeneratorRuntime
was not defined. My .babelrc
file is as follows:
{
"presets": [
["env", {
"targets": {
"chrome": "current",
"node": "current",
"uglify": true
},
"useBuiltIns": true
}]
]
}
I was able to install it successfully by temporarily removing ~/.babelrc
. Perhaps there’s a way to check for it in the user’s home directory before proceeding with installation?
Hmmmm, very interesting.
Unfortunately if we bundle a .babelrc
with the project to override the one it is picking up for you, we would just be bringing the reverse problem (#796) back into play.
@binarymuse is there anything we can do to force the babel
instance Atom is using to transpile the project into not searching for a configuration?
I think that adding "babelrc": false
to the package's Babel config will stop this behavior. See https://babeljs.io/docs/usage/babelrc/#lookup-behavior for more.
I think in older versions of Babel this was perhaps default? I know it at least went by a different config name.
v8.2.1 released which should fix this, thanks for everyone that reported and tracked this down!
I’ve verified that this works with v8.2.1 with my ~/.babelrc
!
Thank you all so much! Its working for me now on 8.2.1!
Issue Type
Bug
Issue Description
Simply updated and it broke.
Bug Checklist
eslint
CLI gives the proper result, whilelinter-eslint
does notLinter Eslint: Debug
command from the Command Palette belowI can't even get that to come up in the commands menu.
[Enter steps to reproduce:]
Atom: 1.17.0 x64 Electron: 1.3.15 OS: Mac OS X 10.11.6 Thrown From: linter-eslint package 8.2.0
Stack Trace
Failed to activate the linter-eslint package
[Enter steps to reproduce:]
Atom: 1.17.0 x64 Electron: 1.3.15 OS: Mac OS X 10.11.6 Thrown From: linter-eslint package 8.2.0
Stack Trace
Failed to activate the linter-eslint package
Commands
Non-Core Packages