Trouble compile Excalibur

[Robert O'Shea]

Having trouble compiling Excalibur so I can test my code for a pull request. I have attached an image of the error I'm getting at compile time and the debug log file

So far I have tried deleting and recloning the project but it doesn't seem to be working for me.

Not sure whether this is a problem with my machine (Mac OSX) or a problem other people are having.

[Erik Onarheim]

Hi Robert,

I can repro this using the latest version of Typescript shown in your logs (2.6.1) I'll open an issue about an upgrade to Excalibur, we might not be able to go all the way to the latest because our docs take a dependency on typedoc which often isnt at the latest version.

The build does seem to work with types...@2.2.2 as a work around.

Let me know if this helps,
Erik

--
You received this message because you are subscribed to the Google Groups "excaliburjs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to excaliburjs...@googlegroups.com.
To post to this group, send email to excal...@googlegroups.com.
Visit this group at https://groups.google.com/group/excaliburjs.
To view this discussion on the web visit https://groups.google.com/d/msgid/excaliburjs/b7a46587-dd48-4771-a0df-4d551dd1f8db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Erik Onarheim]

I've commented on https://github.com/excaliburjs/Excalibur/issues/794 to update typescript

[Kamran Ayub]

I'm not sure why this happened, we've pinned the version of Excalibur and npm should use that version. What version do you have in your node_modules? And using Node 8?

To view this discussion on the web visit https://groups.google.com/d/msgid/excaliburjs/CAMroXaeordVRRguRs5hMrjSy8_0L2ZWtw1ONKi7-g1go5C0k7A%40mail.gmail.com.

[Kamran Ayub]

Sorry I meant pinned version of TypeScript

[Kamran Ayub]

Ah I see you were on Node 7 and npm 3. I think it should work with Node 8 and npm 5. You can use NVM to switch between versions, you'll need to do a full reinstall of the node modules (delete then re run npm install). I think the reason is because your npm is not reading the package-lock.json which is new in npm 5.