Closed LeoAnt02 closed 1 year ago
I've found a working solution by adding this config to my webpack, not sure if this is the right way to go
const config = await createExpoWebpackConfigAsync(
{
...env,
babel: {
dangerouslyAddModulePathsToTranspile: ["moti"],
},
},
argv
);
config.module.rules.push({
test: /\.mjs$/,
include: /node_modules/,
type: "javascript/auto",
});
Are you on the latest moti?
Maybe add moti/skeleton
to dangerouslyAddModulePathsToTranspile
?
I've found a working solution by adding this config to my webpack, not sure if this is the right way to go
const config = await createExpoWebpackConfigAsync( { ...env, babel: { dangerouslyAddModulePathsToTranspile: ["moti"], }, }, argv ); config.module.rules.push({ test: /\.mjs$/, include: /node_modules/, type: "javascript/auto", });
This looks like what the docs recommend.
Is there an existing issue for this?
Current Behavior
The import from the docs for the skeleton loading is not working on my expo project All other import works, and other animations are working with no issues
Also there is no existing npm package called moti/skeleton - I also tried motify/skeleton which seems to be the old version, the npm install but it's not working either in import
Expected Behavior
-
Steps To Reproduce
No response
Versions
Screenshots
-
Reproduction
-