chalk.c | C MACRO library for Colorful Console | Command Line Interface library

Restarting my computer did the trick.. So that's my answer so far. If this happens to you, try restarting pc.

If anyone else has a better explanation of why this happens and if there's a way to avoid it in the future I will mark your answer as correct.

You're hitting the asynchronous nature of Javascript here. readline.question() returns immediately. When your user finishes answering its question it calls its callback. So, the second of your two var socket = io() lines, the one mentioning server, runs before server is defined.

You must do more work in the callback from readline.question() and less work at your outer level.

Edit I'll try to point you in the right direction. Still, you really do need to read up on Javascript and how callbacks are totally vital to its flow of control.

This is not, repeat not, debugged.

The solution can be found here:

https://github.com/kadikraman/draftjs-md-converter/pull/56

It happens because both Babel 7 and draftjs-md-converter define _toConsumableArray function. So, the pull request was issues on the actual github page where it was built with parcel instead and the solution is the following:

Your problem is that console is a singleton object. Each call to addUuidToConsole wraps the previous version of the log/warn/error function in a [yet another] function that prepends a UUID.

What you want is a distinct log object for each of your workers, none of which actually modify the console global object. Instead, each object should provide a console-like API that modifies any arguments passed to it as needed, before forwarding them to the corresponding console method. As it turns out, this is a great use case for the Proxy class.

For example:

If you miss link to your generated style file in index.html then you should search for problem here, because this plugin is responsible for it

I did some googling on this and I think the issue might be with the host value you are setting. Per this Cloud9 support thread which references a similar error:

...You need to use 0.0.0.0 instead since c9user.io is the public address of the proxy. Or modify your /etc/hosts file. echo "0.0.0.0 $C9_HOSTNAME" | sudo tee -a /etc/hosts

So, try setting the host to 0.0.0.0 instead of the public hostname:

If anyone was wondering, I found out the problem. I had to go to chrome://serviceworker-internals and chrome://appcache-internals. I did a search for localhost:8080 and killed those serviceworkers.

I hope this helps whoever this happens to next!

You cannot use both bodyParser and jsonBodyParser middlewares - you have to choose one or the other, it seems.

I ran into the same exact error message, and when I removed the bodyParser middleware and only used the jsonBodyParser, the error went away - my guess is that bodyParser is doing something to manipulate the request body so when the jsonBodyParser gets it, it's no longer well-formed JSON, and fails to parse correctly.

Try with the following command: