-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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
TypeError: Cannot read property 'attach' of undefined at attach #19005
Comments
Experiencing this as well. My It works however, if I install dependencies with my previous Seemingly an issue when jumping from
to
Edit: Can confirm now that the error got fixed by editing
Then remove Side note: I ran into caching issues with |
same issue. everything is ok yesterday. then today this issue come. I'm sure my code have no problem. I think the cause of this issue is about dependencies because when i add yesterday's yarn.lock back.everything is ok . |
hi if you didn't fix the issue, you should try rendering components without Box component. I replaced my Box components with div tag and things got resolved. |
Add "jss": "10.0.0" to dependencies. It is a temporary fix. |
jss was updater few hours ago |
Thanks @un3solka |
Grrr removing Box works though it breaks my styles. |
Si lo hice y funciono !!! Lo bueno es que ya le habia dado estilo a los Box asi que no se rompio nada.... |
Downgrade to an older specific version (4.7.2 in my case, without ^) and install using an older version of |
Funciono para mi ! |
la caja viene con algunos estilos y prefijos predeterminados que se rompieron |
Please provide a full reproduction test case. This would help a lot 👷 . |
Above workarounds didn't work for me. I went into
to
That fixed it for me. Seems the initial call to update is returning undefined. |
@oliviertassinari there you go https://codesandbox.io/s/snowy-sunset-q3fgg Just skimmed this, but it looks like JSS docs seem to do dynamicSheet.attach().update(props); instead |
For those using It should look like this: // package.json
{
"dependencies": {
"@material-ui/core": "^4.8.1",
},
"resolutions": {
"jss": "10.0.0"
}
} |
Thank you soo much! You save my day! |
cross reference: cssinjs/jss#1249 |
THANK YOU <3 |
[email protected] breaks mui, so downgrading for now cssinjs/jss#1249 mui/material-ui#19005
[email protected] breaks mui, so downgrading for now cssinjs/jss#1249 mui/material-ui#19005
I'm using lerna and all the workaround listed above aren’t working for me :/ Should i fix the @material-ui/styles's package version too ? |
the same issue for me too, I tired with "@material-ui/core": "^4.8.0" delete node_moduels ... npm install and the same error after npm run dev |
Temporary fix with pnpm: cat <<EOF >> pnpmfile.js
module.exports = {
hooks: {
readPackage
}
}
function readPackage(pkg) {
if (pkg.dependencies && pkg.dependencies.jss) {
pkg.dependencies.jss = '10.0.0'
}
return pkg
}
EOF Then remove |
Perhaps create a pull request for hotfix? Basically what happened is the new version of Or:
Then run |
Facing the same issue when I upgrade my yarn version 1.17.0 to 1.21.1. package.json: |
I meet the same issues but i solved.
|
appending the following solved it for me, but i've got no idea what's specifically causing this 😕 "resolutions": {
"jss": "10.0.0"
} edit: ah yeah probably this:
hence |
I tried use |
Adding resolutions worked for us, as an extra security we also set material-ui/core to 4.8.0. @popuguytheparrot ensure your package.json is your source of truth: |
@davalapar thanks for the reference - just submitted a PR #19042 |
@favna what about of these packages? |
@popuguytheparrot Just core matters, not the rest. |
I got exactly same error.. I have "@material-ui/core": "^4.8.1",
"@material-ui/icons": "^4.5.1", |
@popuguytheparrot This warning is expected. Just run |
@matthewkwong2 same result |
|
Released under v4.8.2. |
This worked for me. |
Can someone help me out with this issue! When I npm start these arrises.
I have tried with changing the material_ui versions also.
The text was updated successfully, but these errors were encountered: