-
Notifications
You must be signed in to change notification settings - Fork 120
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
Fatal error: Arguments to path.join must be strings #122
Comments
I think the problem is related to this bower/bower#1403 which is fixed in v1.3.8. Problem is that grunt-bower-task is using ~1.2.0 so it won't install the new version. |
Ah, thanks for the clarfication @johnkchiu, I really appreciate it. 👍 Looking like #116 then, is the way to go here. I'll close this one and make a comment in #116 with a "please update to v1.3.8" request. |
Closed
pkaul
pushed a commit
to pkaul/joorino-components
that referenced
this issue
Jul 16, 2014
…ild the project properly again. This depends on fixes of yatskevich/grunt-bower-task#116 and yatskevich/grunt-bower-task#122
baldwicc
added a commit
to baldwicc/cheney
that referenced
this issue
Jan 13, 2015
baldwicc
added a commit
to baldwicc/quail
that referenced
this issue
Jan 13, 2015
igrep
added a commit
to igrep/chrome_mysql_admin
that referenced
this issue
Jun 23, 2015
I tried these commands to according to the README: ```bash $ git clone https://github.com/yoichiro/chrome_mysql_admin.git $ cd chrome_mysql_admin $ npm install $ grunt ``` But got this error: ``` Fatal error: Arguments to path.join must be strings ``` By googling, I found node on my machine and grunt-bower-task are incompatible. Then, I modified the version of the package and make it to build. Pages I found yatskevich/grunt-bower-task#122 # My environment ``` > node --version v0.12.4 > grunt --version grunt-cli v0.1.13 grunt v0.4.5 ``` I might get something wrong because I'm new to node and grunt (and modern JavaScript development). Thanks in advance.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Me:
Problem:
I've tried both the Headroom
git
url and straight version number:A quick Google found this issue:
sapegin/grunt-bower-concat#21
Not sure what that means though.
Anyone else having a problem with the Headroom repo? The Headroom Bower file doesn't look abnormal to me. Should I report the problem via the Headroom repo instead? Is there something they could do to make their
bower.json
more compatible withgrunt-bower-task
?Thanks!
The text was updated successfully, but these errors were encountered: