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

Initial 'grunt build' aborting due to warnings #152

Closed
ryancharris opened this Issue Mar 24, 2016 · 8 comments

Comments

Projects
None yet
3 participants
@ryancharris

After forking and cloning to my local machine I ran npm install, which worked. However, grunt build is aborting due to a missing node module while running the variables task.

cc: #107

screen shot 2016-03-23 at 11 19 14 am

@sfrisk

This comment has been minimized.

Show comment
Hide comment
@sfrisk

sfrisk Mar 24, 2016

Member

What version of Node are you using?

Member

sfrisk commented Mar 24, 2016

What version of Node are you using?

@ryancharris

This comment has been minimized.

Show comment
Hide comment

@sfrisk Node v5.9.0

screen shot 2016-03-23 at 9 14 50 pm

@ryancharris

This comment has been minimized.

Show comment
Hide comment
@ryancharris

ryancharris Mar 30, 2016

@sfrisk Upgraded to 5.9.1 and the build still fails

@sfrisk Upgraded to 5.9.1 and the build still fails

@sfrisk

This comment has been minimized.

Show comment
Hide comment
@sfrisk

sfrisk Mar 30, 2016

Member

I think this might be fixed by a current PR, but let me double check.

ping @arschmitz

Member

sfrisk commented Mar 30, 2016

I think this might be fixed by a current PR, but let me double check.

ping @arschmitz

@arschmitz

This comment has been minimized.

Show comment
Hide comment
@arschmitz

arschmitz Apr 2, 2016

Member

build for node 5.x is fixed by #154

Member

arschmitz commented Apr 2, 2016

build for node 5.x is fixed by #154

@sfrisk

This comment has been minimized.

Show comment
Hide comment
@sfrisk

sfrisk Apr 5, 2016

Member

Going to prioritize pulling in that PR for today's meeting

Member

sfrisk commented Apr 5, 2016

Going to prioritize pulling in that PR for today's meeting

@sfrisk sfrisk closed this in 344d41a Apr 12, 2016

@sfrisk

This comment has been minimized.

Show comment
Hide comment
@sfrisk

sfrisk Apr 12, 2016

Member

@ryancharris, we've pulled in the code that should fix this problem.

Member

sfrisk commented Apr 12, 2016

@ryancharris, we've pulled in the code that should fix this problem.

@ryancharris

This comment has been minimized.

Show comment
Hide comment
@ryancharris

ryancharris Apr 12, 2016

@sfrisk Works on my end. Built without any errors. 👍
screen shot 2016-04-12 at 1 09 23 pm

@sfrisk Works on my end. Built without any errors. 👍
screen shot 2016-04-12 at 1 09 23 pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment