Closed samouri closed 4 years ago
@jakubroztocil / @davidgoli: friendly ping 🏓
Thanks!
Thank you for merging this fix! Not that there's any rush, but what's the release process like?
@samouri I hope to find a time for it over the weekend (unless @davidgoli beats me to it).
Out of curiosity—what is your rrule.js
use case?
@samouri I hope to find a time for it over the weekend (unless @davidgoli beats me to it).
Awesome!
Out of curiosity—what is your rrule.js use case?
I work for AMP, and we use rrule.js
in the amp-date-picker component to support the highlighted/blocked attributes. We've managed to work around this issue in the meantime by manually patching the node_modules
folder. See:
@samouri thanks for the background. ~v2.6.5 is out — https://www.npmjs.com/package/rrule~ The build process is broken, will need to fix that first.
summary Fixes https://github.com/jakubroztocil/rrule/issues/344, and maybe https://github.com/jakubroztocil/rrule/issues/402.
Currently the build produced without timezone support still references
luxon
and expects the code to throw aTypeError
if incorrectly used (done via webpack externals). You can verify this by searching for "luxon" within the contents ofdist/es5/rrule.min.js
.This causes issue when mixed with compilers that don't have the same notion of an external, e.g. Closure Compiler (https://github.com/google/closure-compiler/issues/954). Specifically, the AMP Project is running into when trying to build rrule into our
amp-date-picker
component (https://github.com/ampproject/amphtml/pull/28887).This PR uses NormalModuleReplacementPlugin to replace luxon with a fake implementation that immediately throws.