You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
./node_modules/moment/moment.js
Module not found: TypeCannot read properties of undefined (reading 'startsWith')
Import trace for requested module:
./node_modules/moment/moment.js
./node_modules/moment-timezone/moment-timezone.js
./node_modules/moment-timezone/index.js
./node_modules/date-holidays-parser/src/Equinox.js
./node_modules/date-holidays-parser/src/CalEventFactory.js
./node_modules/date-holidays-parser/src/DateFn.js
./node_modules/date-holidays-parser/src/Holidays.js
./node_modules/date-holidays-parser/src/index.js
./node_modules/date-holidays/src/Holidays.js
./node_modules/date-holidays/src/index.js
I am not sure what is causing this issue, I'm assuming it's some dependency thing between date-holidays, date-holidays-parser, moment-timezone and moment.
I am not sure what is causing this issue, I'm assuming it's some dependency thing between date-holidays, date-holidays-parser, moment-timezone and moment.
If you can't narrow down the area of the problem, there's nothing that any of those libraries' maintainers can do. Each library is working fine in normal circumstances (which we know because there'd be a lot of raised issues otherwise). Given the lack of line numbers in the error trace, it looks to me like a third-party module loading system has thrown the error, which is not possible for us to diagnose.
In addition, creating the same identical issue in 4 repos comes across as quite disrespectful of other people's time.
I am not sure what is causing this issue, I'm assuming it's some dependency thing between
date-holidays
,date-holidays-parser
,moment-timezone
andmoment
.I have my resolutions set to:
and i am using
[email protected]
date-holidays issue: commenthol/date-holidays#487
date-holidays-parser issue: commenthol/date-holidays-parser#59
moment issue: moment/moment#6259
The text was updated successfully, but these errors were encountered: