I ran command from my terminal "live-server public", since my public folder within my project root folder contains index.html, which is the entry point for my web application. However, I am getting the error "env: node\r: No such file or directory". However, I do have the public folder, so what could be the cause of this?
I experienced the same issue (Mac OS Big Sur, 11.6.5), and I discovered that the issue appears for live-server 1.2.2. If you downgrade to version 1.2.1 everything should be fine.
Hope that helps!
Related
I have a project that builds and works on Windows but when I've brought it over to MacOS (Sierra) and set up Resin, Ant, and the rest of my project in IntelliJ the build is failing with a fairly ambiguous error:
build.xml:24: Directory /java/ant-build/classes creation was not successful for an unknown reason
at org.apache.tools.ant.taskdefs.Mkdir.execute(Mkdir.java:70)
Image of the full error message
At first I thought it was a permissions issue but I ran chmod 755 on the two directories and still am getting this error. I also tried updating to a newer version of Ant to replace IntelliJ's built in one with brew install ant#1.9 but that didn't help either.
Does anyone know of any changes that need to be made to projects when migrating from Windows to Mac? I'm the first one at the company to migrate this project to Mac so unfortunately the others don't know much about this.
Both are using:
IntelliJ IDE 2017.1.2
Built in IntelliJ Ant (1.9.4)
Resin 4.0.51
As the comments on the main post point out, this was a permissions issue where the ant was trying to build in the root directory
I had to change my build.properties file so the paths were point towards my $HOME directory.
I have clean install of the latest PhpStorm 2016.1.2 version running on OS X El Capitan. While code completion works perfectly, I can not use path completion at all. If I type ../ I expect to get files/folders suggestion from parent folder, but I only get message "no suggestion". Same thing happens if try relative or absolute paths or only file names without path.
Also if I type path by hand, I can not click on it with cmd and mouse. Path just does not get resolved.
The same code works perfectly with WebStorm on the same computer. Also it works on other identical computers with the same OS X and PhpStorm versions.
I tried clearing cache, creating new project, reinstalling PhpStorm, flushing all PhpStorm preferences (deleting files) but nothing helped.
I found that path autocomplete does not work only when I use common.js require syntax.
Installing node.js plugin to PhpStorm solved the problem.
I am new, so please forgive. I am installing cocotron and ran into an issue while running install.sh. I receive an error stating I do not have writable access to the folder (libraries\Application Support\Developer\Shared\Xcode\Specifications). I'm logged in as admin, it shows I have R/W access - so not sure what's going on.
The folder library\...\Specifications didn't exist - I thought maybe this was the issue so I created the folder - still same issue.
2015 MBP with OS X 10.11
Any thoughts/suggestions would be greatly appreciated.
Had to create the dir path and set permissions in terminal - then it worked.
So I've been using MAMP just fine for an Apache server on Yosemite for some time now. I only need one local host, so I'm using regular MAMP and not MAMP Pro. I am on MAMP 3.4
When I click the "start servers" button, it doesn't respond to the click. It just shows the colored spinner like the application froze, and then nothing happens. Only the SQL server will start but not the Apache.(I don't even use SQL)
I can click through the preferences window just fine, and I can click the quit button, but the start servers button just gives that error.
The Apache box in the top right isn't filled in, and wont let me fill it in either. SQL box is filled it, if that matters. No error message at all. Totally lost.
I ran into the same problem as well after upgrading Mavericks to El Capitan. Mysql did start, but Apache failed starting. I'm running MAMP 3.0.5 (regular version).
I managed to fix this issue by renaming a file in the folder /Applications/MAMP/Library/bin. Rename envvars to _envvars and restart Apache. This made Apache running again on my machine.
Ok im new here but i figured it out.
sudo apachectl stop
Just ran that command.
Try copying the pre update version of your httpd.conf file and restarting apache as recommended above.
sudo cp /private/etc/apache2/httpd.conf.pre-update /etc/apache2/httpd.conf
sudo apachectl restart
This worked for me. I had issues getting MAMP (Pro) to start Apache and when it was running it took a while to shutdown Apache, which is odd since it didn't start.
I blame El Capitan, always blame the captain if things go wrong. Except Captain Morgan, that's your own fault.
Reinstalling MAMP was the easiest way for me as terminal still scares me. But make sure you follow the steps below so you don't lose all of your files and databases!
1. Rename your MAMP folder in Applications/ to "MAMPOLD" so that you don't overwrite your htdocs and databases.
2. Downloaded and install a fresh copy of MAMP from https://www.mamp.info/en/.
3. Replace the 'htdocs' and 'db' folders in your newly installed MAMP with the ones from your "MAMPOLD" folder.
Note that for the db folder I just transferred any folders and files that didn't exist in the new db folder so I didn't replace anything important. This may not be necessary but I didn't want to risk it.
4. Finally when you launch MAMP again you may have to change the ports to default if it isn't working. I had them orginally set to 80 and 3306 which is no longer working so now I have to put up with seeing localhost:8888 which is annoying but at least it's working! If anyone can help me with this I would be grateful.
I found that the ServerRoot in http.conf used the path "/usr" Most Macs use "/users". Soon as I changed it and restart apache MAMP went live
How to fix building workspace problem in Zend Studio?
I'm trying to rename project and rename folder of project, however nothing:
Errors occurred during the build.
Errors running builder 'JavaScript
Validator' on project 'PROJECT'.
java.lang.NullPointerException
you must go to Project->Properties->Builders then disable ‘Javascript Validator’.
The bug has been fixed, you can either wait for the new release or apply the patch :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=318004
I had similar problem and mine is that the saving workspace process try to write in one of the file and it can't even it is available under .metadata directory.
This is how I did:
Open the .metadata directory and look for that particular file, yours can be different, so
change it to read and write for this file then restart eclipse.
It fixed the problem!.
My OS: Ubuntu 10.04 , Eclipse SDK 3.5.2
Hope this help...