-
Notifications
You must be signed in to change notification settings - Fork 292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed date-fns requires #310
Conversation
@jonasclement I just checked this, and wasn't able to reproduce. date-fns exports are still working. |
Interesting. What version of date-fns was installed in your case? For me, it installed version 2.11.0, though forcing version 2.9.0 didn't seem to make a difference. I'm using node version 12.13.0 in my application where I'm getting those errors. |
I'm experiencing this as well. |
@plemarquand @jonasclement can you put together an isolated reproduction example? That way I can take a look at the issue as I am not experiencing it by myself. |
@jonathansamines @jonasclement Sure thing, here is an isolated example. https://github.com/plemarquand/simple-oauth-2-addseconds-bug |
@plemarquand Oh, so the problem is when used along with webpack. Is the proposed fix, actually fix the issue when used along with it? |
@jonathansamines I'm using it along with webpack too, my bad. The fix I proposed worked for me, at least. |
@jonasclement Can I ask you two things:
Thanks for your help! |
@jonathansamines I'll see if I can find time for it, I'll send a new PR. I'm not sure on your other questions, as I'm a relative node/js rookie. Maybe @plemarquand knows. |
I've made the requested changes in #312. |
It looks like
date-fns
changed the way they export their functions, which causes this error when trying to do an authorization code flow:I branched from 3.3.0 as I can see that you've refactored the whole access-token.js file since that release, but from what I've seen you're still calling
require()
in a way that is broken.