Cobus Esterhuyse
Cobus Esterhuyse
+1 for consideration on this. It would be great if it matches the Next.js behaviour.
@captaincole, we ran into the same issue (among many others). For us, the double animation was solved by ensuring we are passing all `props` to the child ``. I _think_...
We have the same issue - dependencies listed in a project-level `package.json` only (as @balintk points out), are not taken into consideration by the rule. Anything imported from those packages...