-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncaught AssertionError: true === false with Atom 1.0.2 upgrade #17
Comments
language-babel v0.10.0, babel 5.6.15 and atom 1.0.2 work for me. spec tests are also working on WIndows and OSX. What version of language-babel and babel-core do you have? babel-core version can be found in package.json at /Users/gbirman/.atom/packages/language-babel/node_modules/babel-core, language-babel version is in settings. AI also need the config.cson for atom ( in particular the language-babel properties ) as it could be a combination of flags. |
I also need any |
Same error for me: $ apm -v
apm 1.0.1
npm 2.5.1
node 0.10.35
python 2.7.6 Also: In config.cson: "language-babel": {} FYI the error is thrown on every JS file even if it is es5. For now I've disabled babel transpilation when no .babelrc file is present which works for me as I don't use es6 in my current project. So I've updated my config.cson to "language-babel":
disableWhenNoBabelrcFileInPath: true |
I can't recreate this. The stack trace indicates the issue is deep inside babel-core and not within atom or language-babel. But something very weird is happening.
The above stack trace shows babel-core under language-babel/node_modules is requiring a module from atom's version of babel-core. The only reason I can think this is happening is if node has cached the ast-types module from a previous use of a file that contains a |
Do any atom packages you use do a dynamic compile by using "use babel"? |
I'm not exactly sure what you mean by
However, I actually have not had any more errors after restarting atom a few times yesterday. Thanks so much for your comments. It will help me try to debug this. I'll let you know if it comes up again. |
@gilbox Thanks for that. I'm pretty sure it's because the package wasn't quite updated completely when you tried to save and we were using a version of ast-types provided by atom that was incompatible. Provided the package was completely updated a reload of Atom would fix the issue. @stephanebachelier Do you still have an issue? |
I'm getting this error too. Node version v0.12.7 AssertionError: true === false |
The problem seams to occur with nuclide-flow with language-babel, so I disabled nuclide-flow, now I'm not getting the error anymore, but I'm getting the following error when I save a js file: "Failed to save remote file: Maximum call stack size exceeded" It only stop occurring when I disable the language-babel pack, I didn't test this on local file, this is happening with me when editing a remote file with nuclide-remote-projects. |
My remote project babelrc has the following:
|
I could manage to stop the error: "Failed to save remote file: Maximum call stack size exceeded" by disabling the "Transpile On Save" option in the language-babel package settings. |
On holiday at the moment but I'll investigate when I return. Are you using Nuclide's remote file option or some other system? |
Just nuclide remote |
@ezsper OK I can't test this as I don't use OSX for dev. Nuclide doesn't support Windows fully e.g. Nuclide remote requires Watchman which isn't available for Windows, nor is Flow supported on Windows. I notice from the stack trace that you use Windows so I don't know how you got it working. |
My remote server is Linux and I have the nuclide server, flow and watchman installed and running there. As far as I know, I don't need to install these in any of my local machine as well, being WIndows, Linux or OSX. Nuclide-remote-projects do a bridge between my local Atom running app on Windows to the Nuclide Server installed on my Linux dev server. So I don't see any incompatibility. |
ok i'll config my Ubuntu server and try to test this. |
@ezsper I can't seem to recreate the problem. Do you still have it or are you not using language-babel? |
Sorry, I really don't know anymore, I was having problems with a couple of other packages with Nuclide and right now, I'm just using es6-javascript package instead and it's working for me. I'm reactivating your package, I'll report if I still get any problems with Nuclide. |
Since upgrading atom today I'm getting this error all the time.
The text was updated successfully, but these errors were encountered: