How can I debug a newly cloned React Native app - reactjs

I am starting to help someone with a new project. This project is React (React Native as is a mobile app).
The project is working fine on her laptop (in her browser), and when I scan the Expo QR code, the app works fine on my Android device.
However, trying to run it in my browser is throwing all these errors:
The 'Can't resolve' error doesn't make sense, because the correct react native files are there. Is this a cache problem? I have tried deleting the .expo/web/cache folder and starting over.
Also, why are there multiple errors in my console, but only one being shown in the information on the actual web page? Does this mean that the single error being shown is causing all the other errors, or it is the only one which needs fixing, or will it show the next error when I fix the one that is being shown?
Thanks

Seems to have been a known problem re babel. See the links below:
https://github.com/babel/babel-loader/issues/173
how to solve this error You may need an appropriate loader to handle this file type

Related

zlibWEBPACK_IMPORTED_MODULE_3.createDeflate is not a function while renderin react-pdf component

I'm using react pdf to render my component as PDF & allow user to download that PDF on button the PDF was working well after applying pollyfills changes but for my lead (who is using MAC) the PDF was not rendering and giving the
Error: react_devtools_backend.js:4026 TypeError: zlibWEBPACK_IMPORTED_MODULE_3.createDeflate is not a function
On deployment it's even works well on his system but locally he can't render it, does anyone have idea what issue that would which causing this things?
I tried to clone the repo in another folder & installed all the dependencies again but nothing works yet
Here's the screenshot of console error: https://cdn.discordapp.com/attachments/990645691531534370/1012846396296138833/Screen_Shot_2022-08-26_at_3.09.51_PM.png
I found the similar issue opened as well source: https://github.com/diegomura/react-pdf/issues/1935
But it's closed without any proper explanation

appropriate loader to handle this file type only inside nodemodules

I am getting this error when trying to open a react native project on the web using expo. If I run expo start and use the cellphone, everything works fine. This only happens when I try to run on the web.
image
Looks like the error is on the line onValueChanged?.(low, high, false); but only happens inside node modules. If I try to use the same syntax inside a file in my project, the compiler works fine. Does someone know how I can fix it?

importing Amplify throws error "null is not an object (evaluating 'keys.filter)" in react native app

Any time I import Amplify into my React Native project's App.js file, I get the following error:
TypeError: null is not an object (evaluating 'keys.filter')
Here is how I'm importing it:
I run the project using Expo only. If I comment the import Amplify line out, any other files which use anything related to Amplify cause the same error to occur.
Initially, when I was loading this project for the first time, I had other errors to deal with like first needing to create the aws-exports.js file. I copied this over from an old project (Because this is meant to be a re-do of another project that's already set up). Once I included that file I had to update a few lines in that file because of an improper reference to Linking from expo. Once I fixed that, it throw this error I'm referencing here. Now, even if I delete the aws-exports file it will throw this error as soon as Amplify is imported into the App.js file.
-- Update
I've found where the error is occurring. Some of my code gets executed but the error happens inside of the reactnative.js file when syncing between two memory software.
I've tried to reproduce this error inside a fresh react application by copying the package.js file and then importing Amplify into the App.js file but it doesn't throw this error.
Here is a screenshot of where the error is taking place. I'm still trying to figure out how to pinpoint where in my code this error begins.
According to Expo, you have to follow these steps
it would be best if you imported Amplify
import Amplify from '#aws-amplify/core'
All you need to follow those steps it sees the configuration issue result data is not coming that's why it gives a null value and crashes.
Follow steps below will fix your problem
https://blog.expo.dev/how-to-build-cloud-powered-mobile-apps-with-expo-aws-amplify-2fddc898f9a2
The problem seems to be resolved by changing the slug attribute in the react app.json file. I changed the slug from being a camel case to an all lower case slug.
After this the error has gone away for what seems permanent. I've been able to replicate the error in small sample apps. I don't understand why this causes these errors.

react native and expo: problem sending log messages symbolicatedStack

Recently I updated react (0.62.2) and expo (37.0.12). Nearly everything works fine. Except upon every App reload and shortly after an error occured, an error screen pops up that displays
console.error: There was a problem sending log messages to your development environment TypeError:
symbolicatedStack.map is not a function. (In 'symbolicatedStack.map(removeProjectRoot)',
'symbolicatedStack.map' is undefined
covering the previously occured error.
since there is no symbolicatedStack written by myself, I suspect its an internal error, but I can't figure out what it is. Upon pressing "Dismiss" everything works fine again. (Till the next reload/error)
Expo / React version are compatible according to their offical websites.
I guess this is dues to version missmatch try running expo upgrade command. It should resolve your issue.

I am new in reactjs and when i was trying to run my first react js project it showing error, it's showing error just after the setup

[these error are showing when i was try to run my first react project. I don't know how to fix please help.][1]
[1]: https://i.stack.imgur.com/Acb0i.pngstrong text
For me, the problem was another instance was running. Search for other react instance running and kill it. It should resume properly after.
Or this is happening because nothing is listening on your adresse:port

Resources