Yea, nevermind. I had a ; in another spot that was actually causing the problem. The traceback on this message from ReactNative sucks because it gives you no idea where that bare ; is. This is NOT an issue.