Closed vanbilt closed 7 years ago
Apologies for the bug. That was my mistake for pushing while still referencing a local fork of the aurelia-cli.
Try checking out tag 0.11.2
first via git checkout 0.11.2
because that is a more reliable release.
git clone https://github.com/shaunluttin/aurelia-open-id-connect.git
cd aurelia-open-id-connect/demo
git checkout 0.11.2
npm install -y
npm run demo
@shaunluttin - Thank You! That does indeed allow me to run the demo.
I'm having other issues with trying to get a "fresh" install of aurelia-open-id-connect
to work - there seem to be issues with oidc-client
expecting more or fewer params - I have not tracked it all down yet - but with the demo running now I'm certain that I will be able to get my project running now.
Thanks again!
Thank you for your help. I've got my local version up and running almost all the way through the full authorization cycle. I'm closing this as your solution solved my issue.
That's excellent to hear @vanbilt. Thank you for opening and then updating the issue.
@vanbilt Time permitting, I'd be interested to know whether release 0.11.4
works with your setup.
Hi Shaun,
If what you were requesting I do was the same steps as above but changing the git checkout
step:
//...
git checkout 0.11.4
npm install -y
//...
Then the answer is yes, 0.11.4
works for me. If that is not what you meant, please let me know, I'd be more than happy to try other things as well.
@vanbilt Yes. That is what I meant. Thank you for testing.
It is a better release, because it builds directly from TypeScript to ES5 instead of using babel as an intermediary, and it also has better source mapping in Chrome, in my opinion.
Also, pull requests are most welcome, if you find the time to doing any fixes, chores, or feature additions to the code.
The first two commands run successfully.
Then I try to
npm install
and I get the following error:I then try to run
npm run
and get the following error: