Olá, eu comecei a mexer com React Native com Expo e fiz uns apps básicos ano passado que nunca deram nada, por algum motivo, desde mês retrasado, qualquer app que eu crie com o expo ele logo que cria o projeto começa a dar erros com coisas que >ele mesmo instalou<. Eu pensei que fosse algum problema de incompatibilidade com algo que tenho instalado entao testei no meu note que foi formatado esses dias, e também tô tendo esses problemas!
Quase sempre os projetos iniciam com erros assim:
"Error: Unable to resolve module postcss from C:\Users\Glory\funecmobile\node_modules\styled-components\native\dist\styled-components.native.cjs.js: postcss could not be found within the project or in these directories"
O projeto mais recente que criei nao teve nenhum b.o, mas ai tentei dar build pra fazer uma apk pra android e testar, que pra minha surpresa agora é somente com o EAS CLI, e sempre que tento dar build ou update falha na última etapa por conta desse erro. Não sei o que fazer pq ainda não encontrei ngm com esses erros usando o expo... Além disso na build também dá outros erros
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
1:"Cannot create styled-component for component: %s.\n\n",2:"Can't collect styles once you've consumed a ServerStyleSheet
's styles! ServerStyleSheet
is a one off instance for each server-side render cycle.\n\n- Are you trying to reuse it across renders?\n- Are you accidentally calling collectStyles twice?\n\n",3:"Streaming SSR is only supported in a Node.js environment; Please do not try to call this method in the browser.\n\n",4:"The StyleSheetManager
expects a valid target or sheet prop!\n\n- Does this error occur on the client and is your target falsy?\n- Does this error occur on the server and is the sheet falsy?\n\n",5:"The clone method cannot be used on the client!\n\n- Are you running in a client-like environment on the server?\n- Are you trying to run SSR on the client?\n\n",6:"Trying to insert a new style tag, but the given Node is unmounted!\n\n- Are you using a custom target that isn't mounted?\n- Does your document not have a valid head element?\n- Have you accidentally removed a style tag manually?\n\n",7:'ThemeProvider: Please return an object from your "theme" prop function, e.g.\n\njs\ntheme={() => ({})}\n
\n\n',8:'ThemeProvider: Please make your "theme" prop an object.\n\n',9:"Missing document <head>
\n\n",10:"Cannot find a StyleSheet instance. Usually this happens if there are multiple copies of styled-components loaded at once. Check out this issue for how to troubleshoot and fix the common cases where this situation can happen: https://github.com/styled-components/styled-components/issues/1941#issuecomment-417862021\n\n",11:"_This error was replaced with a dev-time warning, it will be deleted for v4 final._ [createGlobalStyle] received children which will not be rendered. Please use the component without passing children elements.\n\n",12:"It seems you are interpolating a keyframe declaration (%s) into an untagged string. This was supported in styled-components v3, but is not longer supported in v4 as keyframes are now injected on-demand. Please wrap your string in the css\\\
helper which ensures the styles are injected correctly. See https://www.styled-components.com/docs/api#css\n\n",13:"%s is not a styled component and cannot be referred to via component selector. See https://www.styled-components.com/docs/advanced#referring-to-other-components for more details.\n\n",14:'ThemeProvider: "theme" prop is required.\n\n',15:"A stylis plugin has been supplied that is not named. We need a name for each plugin to be able to prevent styling collisions between different stylis configurations within the same app. Before you pass your plugin to <StyleSheetManager stylisPlugins={[]}>
, please make sure each plugin is uniquely-named, e.g.\n\njs\nObject.defineProperty(importedPlugin, 'name', { value: 'some-unique-name' });\n
\n\n",16:"Reached the limit of how many styled components may be created at group %s.\nYou may only create up to 1,073,741,824 components. If you're creating components dynamically,\nas for instance in your render method then you may be running into this limitation.\n\n",17:"CSSStyleSheet could not be found on HTMLStyleElement.\nHas styled-components' style tag been unmounted or altered by another script?\