SyntaxError: Unexpected token import

[realorangeone]

SyntaxError: Unexpected token import

[RealOrangeOne]

Ahh, I remember the problem. By default, babel (of any kind) doesnt build any scripts that are inside the node_modules directory. One way you could fix this is to mock the native-base module, and just create some empty components, in the same way react-native-mock does it. Or you can use the babel ignore hook on require to compile just that folder (see here)

[RealOrangeOne]

No there is no mocking implementation with react-native-mock that allows you to mock NativeModules. The library I would recommend to achieve this is Mockery. There's some more talk on it over at #11

[RealOrangeOne]

Reading the stack trace, this is coming from a module called native-base. You're solution would be correct. The easiest way to achieve this would be to either upgrade your version of node, as newer ones support import syntax, or you can use something like the babel-node package to do the conversion for you. But this is not a problem with react-native-mock in any way, shape, or form :+1

[devhyunjae]

Yup, i agree this is not a react-native-mock's fault...but this will be a very common issue when trying to shallow test an 3rd party's Component that has import keyword 😢

And I've tried all the approach that you have mentioned. My node version is 6.2.0, which handles 96% compatible, but not working. Tried all kind of babel packages to but fail either.

[jbrodriguez]

Hi @RealOrangeOne, I have a similar case in which I'm using a third party component (https://github.com/corymsmith/react-native-fabric/), while using react-native-mock.

When trying to run a test, I get

/Users/test/app/node_modules/react-native-fabric/Crashlytics.js:11
crash:SMXCrashlytics.crash,
TypeError: Cannot read property 'crash' of undefined

The code is

var { NativeModules, Platform } = require('react-native');
var SMXCrashlytics = NativeModules.SMXCrashlytics;

module.exports = {

  crash: SMXCrashlytics.crash,
  throwException: SMXCrashlytics.throwException,
  .....

It fails because the mocked NativeModules doesn't know anything about a SMXCrashlytics, which is the expected behaviour.

Is it possible to hook into react-native-mock to include a mocked version of SMXCrashlytics (other than forking :) ) ?

[RealOrangeOne]

Closing as not an issue with react-native. Best solution would be to run your tests using something like babel-node so it builds your node_modules, or to mock the library.