React-native-paper: React native Unexpected token, expected ";"

[gron01]

React native Unexpected token, expected ";" error problem

The versions I use :
"react-native": "0.63.2",
"react-native-paper": "4.0.1",
"react-native-vector-icons": "7.0.0",

[github-actions[bot]]

Couldn't find version numbers for the following packages in the issue:

• react-native
• react-native-paper
• react-native-vector-icons

Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.

[gron01]

Hello friends today I got this problem after I deleted my node_modules and installed it again.

[gron01]

The methods I tried.

• Delete and reinstall node_modules.
• ./gradlew clean

[github-actions[bot]]

The versions mentioned in the issue for the following packages differ from the latest versions on npm:

• react-native (found: 0.63.2, latest: 0.63.3)
• react-native-paper (found: 4.0.1, latest: 4.2.0)
• react-native-vector-icons (found: 7.0.0, latest: 7.1.0)

Can you verify that the issue still exists after upgrading to the latest versions of these packages?

[SirKadogan]

I'm getting the same on expo, brand new project.

"expo": "~39.0.2"
"react": "16.13.1"
"react-native-paper": "^4.2.0"

[gron01]

I'm getting the same on expo, brand new project.

"expo": "~39.0.2"
"react": "16.13.1"
"react-native-paper": "^4.2.0"

Version update is not be useful

[gron01]

I updated latest version
And Error:

[pscarey]

I resolved locally by setting:

  "react-native": "lib/module/index.js",

in the package.json of react-native-paper - it appears the default value is redirecting to the Typescript source files.

[github-actions[bot]]

Hello 👋, this issue has been open for more than 2 months with no activity on it. If the issue is still present in the latest version, please leave a comment within 7 days to keep it open, otherwise it will be closed automatically. If you found a solution on workaround for the issue, please comment here for others to find. If this issue is critical for you, please consider sending a pull request to fix the issue.