Jumpei Ogawa

Workaround: Disable browser cache by Browser Developer Tools. If you don't know how, see the following page (Chrome and Firefox): https://www.webinstinct.com/faq/how-to-disable-browser-cache Since this Issue does not happen on production build...

Since this PR is left open without any responses, I'm closing this PR.

Just opened a PR to fix this issue: #63109

@karlhorky Thanks for testing. Yes, \*.config.ts is out of scope of the PR I created this time and not supported yet, unfortunately.

@SalahAdDin Yes, the latest canary release should support \*.config.mjs now. I guess the stable version does not support it yet until the next release.

@mde Snyk send us an email regarding to this vulnerability, so can you check your mailbox? I replied to the email at Feb. 25th 8:00pm UTC. If you no longer...

@mde Thanks for the reply. So you mean I can deprecate the package?

OK, I will deprecate it later. Thanks for confirmation 🙇

I have deprecated this `utilities` package on npm. I keep this issue open so that you can resolve this vulnerability in case you want to restart the maintenance for `utilities`...

@mde I think we should also flag this package on npmjs.com so that `npm audit` can tell the users this package is vulnerable. I asked npm support how to register...