-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Remove console.log statement #1
Comments
If you somehow actually run into the console.log in your code then you're using the dependency wrong. So there's no harm for the small Easter egg to be there. Please give me an example where you ran into the console log. |
This means that whatever dependency you're ignoring is still being accessed and the |
Version 1.1.0 has been published which removes the line. Update the version in the resolutions string to the following to start using it.
|
I believe you're right and think I understand why we're seeing the message. I'm using this package (as others do too) to build Thanks for the fast response! |
Hm, there is a, perhaps unintended, difference between the two versions: Version 1.0.2 works fine, 1.1.0 does not (can't find module ...). This is how I include the package in package.json (the addition works, the removal doesn't):
|
And here I was hoping I could improve the package a bit... I'll have to look into this then. Is this repo where you're using gifsicle open source so I can use it to test @jorissteyn ? |
Yeah see the comment in Klathmon/imagemin-webpack-plugin#113 |
@jorissteyn I tried to reproduce it but I couldn't get to give me any error. That said, I did publish v1.1.1 where I moved the index files out of |
Confirmed v1.1.1 works like a charm, thank you! |
That's good to hear, then I'll close this issue. |
Summary: After the React Native 0.70 upgrade, I noticed a statement saying something like "wow you found the file, here's a cookie 🍪". I couldn't find that anywhere on GitHub or via `git grep`, so I ran `grep -R 🍪 .` in the root in the repo and found what was going on. The source was the `@favware/skip-dependency` package. I found [this issue](favware/skip-dependency#1) on their GitHub, which revealed that the line got printed when the dependency being replaced by `@favware/skip-dependency` was included. It's there as a sort of canary to indicate that the replaced package is still being imported, and to warn of any possible issues that may result. In our case, the import is occurring in `@react-navigation/devtools`, but since we're not using `useFlipper` from that package, nothing is done with the import, so we are safe. To turn off the warning, I updated the package to a version that no longer printed the error, as advised in the linked GitHub issue above. Test Plan: Confirm the cookie message was no longer getting printed in the React Native logs Reviewers: tomek, bartek, atul Reviewed By: tomek, bartek Differential Revision: https://phab.comm.dev/D6194
It's not helpful
The text was updated successfully, but these errors were encountered: