Picture of Chris Gillison
Promise rejection warning
by Chris Gillison - Friday, 2 August 2019, 10:02 AM
 

Hi all,

I've just set up a new PC & installed the framework with no errors. Unfortunately, now a project I've been working on for some time won't build properly. I'm getting an UnhandledPromiseRejectionWarning during the compile and I have absolutely NO idea what that is!

I attach screenshots of the error and of the versions of node, grunt, adapt etc I'm using. Please could someone help me get back up and running?

(As a test I created a new course using adapt create course then did a grunt build and the build completed fine with no errors)



Picture of Matt Leathes
Re: Promise rejection warning
by Matt Leathes - Friday, 2 August 2019, 11:24 AM
 

Well it's not a part of Adapt that I know much about but it seems to be the code that's checking plugins for references to old paths to adapt.css etc that's failing. It was all introduced in this PR. No idea why it should suddenly stop working for you though. Anything you've changed recently in any of those files that could be affecting it?

Picture of Chris Gillison
Re: Promise rejection warning
by Chris Gillison - Friday, 2 August 2019, 12:18 PM
 

Not the I'm aware of.

I have everything in svn apart from the node_modules. So I checked out the course onto the new PC then ran a new adapt create course to get a node_modules folder, then copied that folder into the root of the course. Could it be that this new folder is different in some way? This course was probably created about a year ago.

Picture of Chris Gillison
Re: Promise rejection warning
by Chris Gillison - Friday, 2 August 2019, 2:52 PM
 

Hi Matt,

So I'm back up and running, thankfully. I deleted the newly created node_modules folder then copied over the node_modules folder from the course on my old PC. grunt build is now working with no errors.

What I did notice was that the old node_modules folder has 15,790 files in it, but the newly created one only has 11,823 files. I'm rather clueless as to what all these files are but I'm guessing the change in the makeup of the node_modules folder since the course was orginally created (May 2018) had caused this problem.