-
Notifications
You must be signed in to change notification settings - Fork 397
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
Vizceral Transpile Breaks on Lodash #33
Comments
Did you run Keep in mind that this module is used regularly at each published version so transpiling does work in general. If something is not working specifically for you, please try to include a lot more detail (node version, npm version, OS, make sure you're testing from a clean clone and install...) |
Just ran:
The node_modules were deleted prior. I even ran an |
Ah, you're trying to run scripts from inside the node_modules directory. That's a workflow I have never run across. The match to run babel was a regex on node_modules, so it was never being transpiled. |
Nevermind, just realized that this fixes the one error seen when trying to transpile inside the node_modules directory, but it breaks the output. Reverted this change. We don't support running npm run build inside of a node_modules directory. Use |
@jrsquared thank you. I was running:
Hopefully others won't make the same mistake. I put a BUILD.md inside my own custom vizceral build with this note. Essentially what I'm doing is putting the transpiled source into a lib/vizceral and that's all being distributed by Gulp and served up as a single main.min.js file to my Angular UI. |
With the latest 3.0.6 I run the following:
npm install && npm run build
And am receiving this error:
ERROR in vizceral.min.js from UglifyJS SnytaxError: Unexpected token: name (_) [./src/vizceral.js:18,0]
The text was updated successfully, but these errors were encountered: