-
Notifications
You must be signed in to change notification settings - Fork 40
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
Uncareted sanitize.css
dependency causing failure while requiring postcss-normalize
#58
Comments
temp solution for package.json
|
So, @10hendersonm, would an appropriate solution be to protect that code from throwing and releasing that in patch today? Or to force I can definitely "coordinate" this. |
I'll be 100% honest that this isn't my usual space. I dropped a PR (#59) but haven't had a chance to check this repo's normal workflows yet to see if I missed any other requirements. |
Oh, hah, @jonathantneal I didn't realize you have |
I was also having the same problem where the sanitiza.css was somehow not found. The suggested workaround worked for me. |
Can confirm this issue causes
|
I have the same question :'cannot find module ‘sanitize.css/page.css’' |
@LQ0611 for now, a temporary fix would be to pin Add this in your
|
Oh, yeah,i do this now. and I hope this question could be completely solved .thank you very much
… 2021年9月15日 下午3:32,Raj Rajhans ***@***.***> 写道:
@LQ0611 <https://github.com/LQ0611> for now, a temporary fix would be to pin sanitize.css to 12.0.1.
Add this in your package.json
"resolutions": {
"sanitize.css": "12.0.1"
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#58 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJ5NG54LK3S3MGCMYCRM3H3UCBDYPANCNFSM5EAQJATQ>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
It only works on |
yeah,' resolutions' is a temporary way, of course , the base way is that the problem is resolved by owner , hahaha |
1,maybe someone useing pages.css? |
Without updating the |
the right thing to do is revisit https://github.com/csstools/postcss-normalize/blob/HEAD/CHANGELOG.md#900-april-12-2020 which introduced the |
@bmuenzenmeyer, aye. For now, I’m side-stepping the issue by using |
[email protected]
removes filepage.css
, which is directly referenced incssMap.js
:postcss-normalize/src/lib/cssMap.js
Line 16 in 5b80f53
As
sanitize.css
is installed at version*
rather than something like12.0.0
or^12.0.0
,npm
users are auto-upgraded into this breakingsanitize.css
version. This includes users ofcreate-react-app
'sreact-scripts
.The text was updated successfully, but these errors were encountered: