Vizceral Transpile Breaks on Lodash about vizceral HOT 5 CLOSED

Did you run npm install fresh or is this in an existing vizceral directory? If it's a directory that has already been used, make sure you run npm update as well.

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...)

from vizceral.

Just ran:

npm install [email protected] && cd node_modules/vizceral && npm install && npm run build

The node_modules were deleted prior. I even ran an npm update and repeated the install and build stages and am receiving the same aforementioned error.

from vizceral.

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.

from vizceral.

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 git clone to get the source and build if you need to build it, and npm link if you want to use your own modified vizceral.

from vizceral.

@jrsquared thank you. I was running:

npm install vizceral
cd node_modules
cd vizceral
npm install && npm run build

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.

from vizceral.