linemanjs / lineman

Lineman helps you build fat-client JavaScript apps. It produces happiness by building assets, mocking servers, running specs on every file change
MIT License
1.18k stars 83 forks source link

Why does 'npm install lineman-less' say I am missing a file at '/Users/peteheard/app/css/main.less'? #330

Closed peterheard01 closed 8 years ago

peterheard01 commented 9 years ago

I am totally flummoxed by this.

I have re-installed node. I have reinstalled lineman globally. I have cleared the npm cache.

But when I download the lineman-angular-template and run....

npm install or npm install lineman-less

I get this error....

screenshot 2014-11-01 13 13 45

Why on earth would installing lineman-less want me to have a less file in my own user directory? Totally can't get my head around it! Help!

:-)

searls commented 9 years ago

Great question. Versions of everything?

peterheard01 commented 9 years ago

Well it was just the stock template from github. Simply downloaded and tried to run npm install so the versions are the same as what is in Github which was working last week and I know it worked locally...

But wait, NEWS FLASH....

I was unzipping the template, running on my desktop and doing it and getting problems. When I unzipped in my downloads folder /stuff/petedl then ran 'npm install' magically it works and lineman less is installed. WTF? Has my desktop got some different way of running npm or somehing?

searls commented 9 years ago

That would be the next thing to check

On Sat, Nov 1, 2014 at 10:49 AM, Pete Heard notifications@github.com wrote:

Well it was just the stock template from github. Simply downloaded and tried to run npm install so the versions are the same as what is in Github which was working last week and I know it worked locally... But wait, NEWS FLASH....

I was unzipping the template, running on my desktop and doing it and getting problems. When I unzipped in my downloads folder /stuff/petedl then ran 'npm install' magically it works and lineman less is installed. WTF? Has my desktop got some different way of running npm or somehing?

Reply to this email directly or view it on GitHub: https://github.com/linemanjs/lineman/issues/330#issuecomment-61370447

peterheard01 commented 9 years ago

Well I have OSX showing hidden files and there is nothing. I repeated the experiment again and same problem. So I can't build a lineman-angular project on my desktop but I can in other folders.

If anyone has any ideas I would love to know because there must be something happening from the desktop that doesn't happen in folders. Urrrrg what an irritating problem. Not big. Just weird. Thanks for the bounce anyway.

searls commented 9 years ago

I mean can you please provide the version of node and npm on each machine you did this on?

On Sat, Nov 1, 2014 at 11:02 AM, Pete Heard notifications@github.com wrote:

Well I have OSX showing hidden files and there is nothing. I repeated the experiment again and same problem. So I can't build a lineman-angular project on my desktop but I can in other folders.

If anyone has any ideas I would love to know because there must be something happening from the desktop that doesn't happen in folders. Urrrrg what an irritating problem. Not big. Just weird. Thanks for the bounce anyway.

Reply to this email directly or view it on GitHub: https://github.com/linemanjs/lineman/issues/330#issuecomment-61370854

peterheard01 commented 9 years ago

NODE : v0.10.33 NPM : '1.4.28' OSX Yosimite 10.10

Come to think of it this problem only happened when I started using Yosimite, like this week.

searls commented 9 years ago

Can I have your version of node AND npm on each machine? I thought you were doing this from two machines?

On Sat, Nov 1, 2014 at 11:06 AM, Pete Heard notifications@github.com wrote:

NODE : v0.10.33 OSX Yosimite 10.10

Come to think of it this problem only happened when I started using Yosimite, like this week.

Reply to this email directly or view it on GitHub: https://github.com/linemanjs/lineman/issues/330#issuecomment-61370989

peterheard01 commented 9 years ago

No, just one machine. It's the desktop that is the problem. Any other folder it's okay. I updated the NPM number above....

jayharris commented 9 years ago

@peterheard01 I know this is an old issue, but do you happen have a package.json in Users/peteheard?

jasonkarns commented 9 years ago

sounds like this is likely: jasonkarns/node-find-root-package#1