Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A trailing comma is not permitted after the rest element #29

Open
icastillejogomez opened this issue Dec 18, 2018 · 4 comments
Open

A trailing comma is not permitted after the rest element #29

icastillejogomez opened this issue Dec 18, 2018 · 4 comments

Comments

@icastillejogomez
Copy link

When I import the module appers this error:

/app/node_modules/react-native-scrollable-tab-view/SceneComponent.js: A trailing comma is not permitted after the rest element (9:32)

   7 |
   8 | const SceneComponent = (Props) => {
>  9 |   const {shouldUpdated, ...props, } = Props;
     |                                 ^
  10 |   return <View {...props}>
  11 |       <StaticContainer shouldUpdate={shouldUpdated}>
  12 |         {props.children}
@UzairAhmedSiddiqui
Copy link

any update on this?

@saikiranoptisol
Copy link

@UzairAhmedSiddiqui you can just have a work around on this by removing , in
const {shouldUpdated, ...props, } = Props;
in the node_modules/react-native-scrollable-tab-view/SceneComponent.js

@chhavi-khandelwal
Copy link

Honestly, that is not a workaround. node modules are never committed. This will only work if you are working on a local environment. Please fix this

@enaiho
Copy link

enaiho commented Jul 5, 2021

When I import the module appers this error:

/app/node_modules/react-native-scrollable-tab-view/SceneComponent.js: A trailing comma is not permitted after the rest element (9:32)

   7 |
   8 | const SceneComponent = (Props) => {
>  9 |   const {shouldUpdated, ...props, } = Props;
     |                                 ^
  10 |   return <View {...props}>
  11 |       <StaticContainer shouldUpdate={shouldUpdated}>
  12 |         {props.children}

Also experiencing similar issue as well. Any resolution yet on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants