-
Notifications
You must be signed in to change notification settings - Fork 193
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
Chore/deps swc 220 plus workaround #1218
Conversation
Socket Security Pull Request ReportDependency issues detected. If you merge this pull request, you will not be alerted to the instances of these issues again. 📜 Install scriptsInstall scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.
Pull request report summary
Bot CommandsTo ignore an alert, reply with a comment starting with
Powered by socket.dev |
362336e
to
d36633c
Compare
what is this one about? |
Adjusted the description |
is this still active or can we close it? |
We should solve this |
so then let's solve this. July is already very old. |
It's about priorities. Happy to touch this after the manifest. |
8a45935
to
89da2d2
Compare
🚀 Thanks for the pull request! Here are the current build files for testing: Download and unzip the file for your browser. Refer to the readme for detailed install instructions. Don't forget: keep earning sats! |
8cb1303
to
466315e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I added the link to the swr discussion to the description for later documentation.
I think, your current fix with removing spyOn
is ok for now.
Thanks, already watching that discussion. |
…eanup chore: remove outdated md-files and adjust feature-template options
13e7867
to
e2cb931
Compare
Latest swc updates break our Jest setup. There's is a workaround but we still need to adjust our setup.
Staying on
v205
is currently working for us.SWR and Jest
See this discussion for SWR with Jest
=> swc-project/swc#5151 (comment)