Skip to content
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

Module not found: TypeCannot read properties of undefined (reading 'startsWith') #1122

Closed
bigbizze opened this issue Oct 15, 2024 · 1 comment

Comments

@bigbizze
Copy link

bigbizze commented Oct 15, 2024

./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 have my resolutions set to:

  "resolutions": {
    "date-holidays-parser": "^3.4.4",
    "moment": "^2.29.4",
    "moment-timezone": "0.5.43"
  },

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

@gilmoreorless
Copy link
Member

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.

@gilmoreorless gilmoreorless closed this as not planned Won't fix, can't repro, duplicate, stale Oct 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants