-
Notifications
You must be signed in to change notification settings - Fork 13
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
[JS] Build failure - Couldn't find preset "jolt" relative to directory #3
Comments
Hi @ylac, since the package is already transpiled, it shouldn't be using the babel config. Can you try resetting the packager cache? I'll update the package in our apps and see if I can reproduce this |
Hi @negativetwelve, yeah I tried resetting the packager cache but it didn't help. I just reverted to 1.0.0 and it builds ok. Btw, I think there's a typo in the docs, heap.event should be heap.track? |
hmm okay I'll definitely get this babel issue fixed today. Yeah, that's a typo, I can fix that as well (unless you want to submit a PR? :) |
Great thanks, I just submitted the PR (my first ever :) ). |
Awesome, that's exciting :) thanks for contributing! |
Looks like you stumbled on a pretty big react-native issue @ylac:
and the big one: facebook/react-native#10966 I'll fix up the packages tonight (I just switched all of them to an "babel" key under package.json :( thanks again for pointing this out! |
This has been fixed and released as v1.3.0 https://github.com/negativetwelve/react-native-heap-analytics/releases/tag/1.3.0 |
Hi,
I'm having an issue after upgrading from heap-analytics 0.2.0 to 1.1.2. On build I get the error: "TransformError: /Users/[user]/Desktop/spot-save/node_modules/react-native-heap-analytics/build/Heap.js: Couldn't find preset "jolt" relative to directory "/Users/[user]/Desktop/spot-save/node_modules/react-native-heap-analytics".
I've tried reinstalling the pod, and have also set the header search path to recursive. I'm on react-native 0.44.3.
Any help would be greatly appreciated.
The text was updated successfully, but these errors were encountered: