babel-relay-plugin-loader | Babel Relay Plugin in .babelrc and using babel | Plugin library
kandi X-RAY | babel-relay-plugin-loader Summary
kandi X-RAY | babel-relay-plugin-loader Summary
This workaround enables us to use the Babel Relay Plugin in .babelrc without breaking babel-node.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of babel-relay-plugin-loader
babel-relay-plugin-loader Key Features
babel-relay-plugin-loader Examples and Code Snippets
Community Discussions
Trending Discussions on babel-relay-plugin-loader
QUESTION
I followed the Relay tutorial for getting started after doing the create-react-app to get a new react up and running. I ran it both in TypeScript mode (from here: https://github.com/Microsoft/TypeScript-React-Starter) and also in the normal JavaScript mode and came to the same result initially.
This is the error I'm getting when I try and run the app:
Either the Babel transform was not set up, or it failed to identify this call site. Make sure it is being used verbatim as
graphql
My suspicion is that Babel was just not running at all, but I'm not sure if that's completely true. I followed this: https://hackernoon.com/using-create-react-app-with-relay-modern-989c078fa892 to see if that would help get my babel executing within my new create-react-app + relay app with no luck. I even ejected the app from create-react-app and modified the webpack to get it working. Below are what I believe are the relevant files. I've done a ton of searching on this topic with no such luck and can't find an example that's using React + Relay Modern + Graphql.
package.json
...ANSWER
Answered 2018-Mar-20 at 13:34I ran into this exact issue on the same tutorial. Basically, this is a Babel configuration issue. There are ways to jump through hoops getting this to work with create react app but the easiest way it to just eject the app and do the following steps:
Run react-scripts eject
(make sure react-scripts
is installed globally)
Adjust your Webpack config to include 'babel-loader'
:
QUESTION
JS newb here:
I've spent a couple days on this bug, and I've looked at many answers and practiced my most earnest Google-Fu, and tried many different babel plugins and presets configurations, as well as tried migrating my webpack 1 project into a webpack 2 incarnation, and in the end I'm still hitting the same wall. Please give me an assist.
When I try to build my project, all open sourced here, and most recently active and relevant to this question in the webpack2migration branch, I've been unable to build for production (and not even dev after futzing more and more with it through unproductive debugging)
This is the error I haven't gotten around, admittedly because I don't understand some (maybe many) of the complexities in webpack and how babel is to be correctly configured for what I'm struggling with.
Here's the error:
...ANSWER
Answered 2017-Jul-05 at 06:47You code is importing separate source file from node_modules folder react-google-maps/*src*/lib/async/withScriptjs.js
But your webpack rules exclude files in node_modules from babel compilation process
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install babel-relay-plugin-loader
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page