Closed SleeplessByte closed 2 years ago
is the framer issue a web issue only?
Yes, because framer-motion
is not imported on native (as far as I can tell)
it is imported on native, so this must be an expo web issue. it works fine for me with next.js
Do you set up next.js differently (like, is it not using webpack)? It feels like a babel/webpack issue, and that would indeed point to expo web's configuration.
no, I think it's just an issue with expo's webpack config or something
does this help?
webpack.config.js
const createExpoWebpackConfigAsync = require('@expo/webpack-config');
module.exports = async function(env, argv) {
const config = await createExpoWebpackConfigAsync(env, argv);
config.resolve.alias['framer-motion'] = 'framer-motion/dist/framer-motion';
return config;
};
I got the idea to alias the imports from here: https://stackoverflow.com/a/70387589/7869175
@nandorojo Thanks
@nandorojo yes.
I had to rm -rf .expo/web
after doing a fresh node_modules
, but it then worked.
Is there an existing issue for this?
Workaround
https://github.com/nandorojo/moti/issues/199#issuecomment-1134805495
Current Behavior
I've started upgrading to expo 45
framer-motion
.Now, I assume that the framer-motion issue is actually upstream / has to do with how webpack is importing the dependency, but I couldn't find in the instructions how to make this work. Perhaps you have some guidance?
Expected Behavior
It works without these errors
Steps To Reproduce
npx create-react-native-app -t with-moti
yarn add expo-cli -D
yarn expo upgrade
Y
(proceed)Y
(upgrade to 45.0.0)0.17.1
yarn install
yarn web
(it doesn't work)0.18.0
yarn install
yarn web
(it doesn't work)Versions
Screenshots
No response
Reproduction
https://github.com/SleeplessByte/broken-moti-18-expo-45