-
Notifications
You must be signed in to change notification settings - Fork 7
Firefox fails to run (errors) when using frozen-moment with webpack #21
Comments
@ericlau-solid Thanks for the report. This seems likely to be an issue with how I set up CommonJS module support, which was focused on the Node environment rather than tools like Webpack. Can you try the code in #22 and let me know if that helps? |
@ericlau-solid Did you ever get a chance to try #22? That said, the code where you're getting a syntax error is one of the core library's locales, so I'm not sure why that'd webpack differently with Frozen Moment than without. Also, FYI, I'm working with Moment's maintainers to get an officially-distributed and supported version of Frozen Moment's functionality. I'm hopeful that moving this functionality closer to core will also help webpack do the right thing. |
I have no time or chance. Have serious health issue that I must focus on. Eric Lau - Gmail On Sat, Jul 16, 2016 at 7:48 AM -0700, "Lucas Sanders" [email protected] wrote: @ericlau-solid Did you ever get a chance to try #22? That said, the code where you're getting a syntax error is one of the core library's locales, so I'm not sure why that'd webpack differently with Frozen Moment than without. Also, FYI, I'm working with Moment's maintainers to get an officially-distributed and supported version of Frozen Moment's functionality. I'm hopeful that moving this functionality closer to core will also help webpack do the right thing. — |
Okay, no problem. Good luck with your recovery! I'll close this issue for now, but feel free to reopen and/or comment on #22 if you ever get back to this in the future. |
Issue only happens on firefox. Chrome runs fine. Only happens using frozen-moment. Moment itself webpacks fine with same settings.
Line with syntax error reads:
The text was updated successfully, but these errors were encountered: