-
Notifications
You must be signed in to change notification settings - Fork 57
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
Update developer build instructions #15
Comments
Thanks for bringing this to our attention. I just updated the repo with the added Can you provide more information on the When running |
Thanks for adding Regarding the second part:
skipping a bunch of compiler errors where node tries and fails to build the module from source
It says it is an optional dependency, so maybe we are ok. Nope. Running
However, |
Thanks for the additional feedback. I'm looking into this, too.
but then everything seems to work. I'm on a mac, node 8.11.1, npm 5.6.0, grunt 1.0.1, grunt-cli 1.2.0, bower 1.8.4. Could you provide those version numbers for your system and I'll see if I can repro? Thanks! (Edit -- i see from above you're on node 10.6, npm 6.1, and I'm seeing the same errors with those versions) |
Glad you could reproduce the error. Interesting that it is ok with the older versions. Thanks for looking into this. Hopefully the maintainer of those modules can be of some assistance. |
we're also still looking at things from our end, testing if we can update the package that's causing this problem. |
ok, try deleting |
Now
As an alternative with
|
hey, sorry it's taken so long to get back to you on this. we were all out at our User Conference last week. I'm seeing the same thing with we haven't seen this in our dev environments because we've been using node 8.x. switching to 10.6.0, i see the same thing there as well. it may take some time to track down what's happening in node 10.6 (and why |
I ran into this same problem using node v12.1.0. |
Greetings has this issue been resolved? I continue to get the below error: added 740 packages from 414 contributors and audited 4912 packages in 80.343s D:\DEPLOYMENTS\storymap-cascade-master\storymap-cascade-master\src\app>yarn install D:\DEPLOYMENTS\storymap-cascade-master\storymap-cascade-master\src\app>gurnt D:\DEPLOYMENTS\storymap-cascade-master\storymap-cascade-master\src\app>grunt
Running "jshint:nls-all" (jshint) task
Running "eslint:target" (eslint) task D:\DEPLOYMENTS\storymap-cascade-master\storymap-cascade-master\src\app\storymaps\tpl\print\media\Text.jsx D:\DEPLOYMENTS\storymap-cascade-master\storymap-cascade-master\src\app\storymaps\tpl\print\PrintViewReact.jsx ✖ 3 problems (0 errors, 3 warnings) Running "clean:build" (clean) task
Running "clean:deploy" (clean) task
Running "clean:jsapioptim" (clean) task
Running "clean:fonts" (clean) task
Running "mkdir:all" (mkdir) task Running "copy:fonts" (copy) task Running "copy:fonts2" (copy) task Running "copy:fonts3" (copy) task Running "copy:youtube" (copy) task Running "copy:calcite-vars" (copy) task Running "copy:less-in-react" (copy) task Running "copy:hbs-in-react" (copy) task Running "babel:dev" (babel) task Running "copy:commonResources4react" (copy) task Running "requirejs:builder" (requirejs) task |
Building per the instructions in the readme (V1.8.3), left me with errors because the vimeo player was not installed. This appears to be listed in bower.json, but not package.json file. Installing bower and then running
bower install
seemed to do the trick.Also
npm install
generated errors because the prebuilt binary for [email protected] was unavailable for darwin (mac osx).yarn install
worked fine. This could be a transient error, but I'm left wondering what the correct build process is.The text was updated successfully, but these errors were encountered: