-
Notifications
You must be signed in to change notification settings - Fork 27.3k
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
Error using transform-define #1292
Comments
Strangely enough, it works when I change to |
|
OK it's because my custom server is normally simply started with I'll try to adapt the babel config not to load that plugin in It's not trivial to get all the universal config right... |
@tim how can I set up my babel config, so that it doesn't transpile a certain folder (server/)? |
An example of using transform-define for universal configuration is provided, but I have a weird error, which I narrowed down below (run it with babel-node):
Somehow next manages to load my app based on the above principle just fine, but the
console.log
throws when I run the server myself (I'm trying to add integration tests):The text was updated successfully, but these errors were encountered: