-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Fix Dropzone following #15315 #15353
Conversation
go-gitea#15315 appears to have caused a change in the way Dropzone is imported - and it now produces a module rather than the constructor. This PR rather hackily just adds another Dropzone call to the result. Signed-off-by: Andrew Thornton <art27@cantab.net>
@silverwind - you got any ideas? (git bisect narrowed it down to #15315 as the causative commit.) |
Interesting. I would not have thought that webpack suddenly behaves differently in terms of import handling with the The proper fix would be |
It's so weird. I'll push the proper fix here. It doesn't seem any other imports are affected. |
make L-G-T-M work |
#15315 appears to have caused a change in the way Dropzone is imported - and it
now produces a module rather than the constructor.
This PR rather hackily just adds another Dropzone call to the result.
Signed-off-by: Andrew Thornton art27@cantab.net