Closed phillipadsmith closed 7 years ago
@phillipadsmith Could you specify the Node.js version you are using?
@kamikazechaser
➜ concierge-plus-br git:(master) ✗ node -v v5.9.0
@phillipadsmith I'm trying to test Concierege but I end up getting a "!CORE!" threw up. <unknown> is now covered in sick.
I'm trying to test Concierege but I end up getting a "!CORE!" threw up.
is now covered in sick.
Hmmm... that's not good.
What steps did you take to test?
cc @mrkno
@phillipadsmith @mrkno
Installation Bit
git clone https://github.com/concierge/Concierge.git
cd Concierge
npm install
npm start
Running The Bot
/kpm install telegram
/kpm config telegram username "aaaaabbb:CCC888999" (My Actual Bot Token Here)
/kpm config telegram commandPrefix "/"
/kpm start telegram
It returns
"!CORE!" threw up. <unknown> is now covered in sick.
Odd. That's not what happened for me. What version of Node?
Tested on both v6.5.x and v7.2.x
Okay, let me give that a try...
@kamikazechaser It's a documentation error (I'll fix up now). Try:
/kpm config telegram token AbcXyz
Telegram requires a token property, not a username property.
However, @mrkno, should the error message from Concierge be more helpful than that?
If you don't start with the --debug
argument it suppresses stack traces (and cause the core loader failed to load your module, rather than your module actually loading then failing it assumes that the core platform was at fault, hence !CORE!
) as many stack-traces from Concierge aren't actually problems with Concierge itself.
Not entirely certain why you are getting your exception however, cause if babel is loading correctly it should be editing your code to have a
Concierge babel does not touch "use strict";
at the top.npm
modules, and your version of node is old enough that it won't allow ES6 const
and let
without "use strict";
defined in each file (babel does this for all other files in Concierge). If both https://github.com/GochoMugo/tgfancy/blob/master/lib/client.js and https://github.com/GochoMugo/tgfancy/blob/master/lib/index.js have this defined at the top of them, it will solve this problem in older versions of node.
If you don't start with the --debug argument it suppresses stack traces (and cause the core loader failed to load your module, rather than your module actually loading then failing it assumes that the core platform was at fault, hence !CORE!)
Makes sense.
Concierge babel does not touch npm modules, and your version of node is old enough that the ES6 const and let without "use strict"; defined in each file (babel does this for all other files in Concierge). If both https://github.com/GochoMugo/tgfancy/blob/master/lib/client.js and https://github.com/GochoMugo/tgfancy/blob/master/lib/index.js have this defined at the top of them, it will solve this problem in older versions of node.
Okay, confirmed with v7.2.1 that there's no error message.
However, I'm having other issues, which I'll ask about in the Concierge repo.
Thanks @mrkno !
For completeness, I suggest you use the latest Node.js version which supports ES6 out of the box. I am not seeking to support older Node.js versions, in a bid to force people to use the newer versions. Sorry about that!
@GochoMugo No need to apologize; I completely understand. :-)
@phillipadsmith I suggest you manually add the 'use strict'
in the tgfancy files in node_modules/ folder. You should still be able to use tgfancy with the older versions, I believe so! 😉
@GochoMugo Being blissfully ES6 ignorant, I'm stuck trying to update the Telegram module for Concierge (previously known as Kassy) with the following error:
This is a vanilla/default install of Concierge with the existing Telgram integration loaded, and where I've substituted
tgfancy
fornode-telegram-bot-api
When I try to start the integration, it fails per the above message.Any help around my ignorance here greatly appreciated. :-)