I am following the developers.squarespace.com documentation and I am trying to use a local dev environment to make my static website into a squarespace template. As far as getting the server started, everything is working fine until I get to the point of installing the squarespace server to my system. To beging, I use this command in my Mac's terminal:
npm install -g #squarespace/server
After I enter this, everything once again seems to be working correctly because I am met with this (which doesn't show any errors as I have seen for others):
Executing: npm run bundle
> #squarespace/server#1.1.2 bundle /Users/Squid/.npm-global/lib/node_modules/#squarespace/server
> node scripts/bundlejre.js --accept --clear -tz -j 8u131 -o build/distributions/runtimes/jre
Bundling compatible JRE (This may take a while)
> #squarespace/server#1.1.2 cleanupscript /Users/Squid/.npm-global/lib/node_modules/#squarespace/server
> node scripts/execif.js --os=win32 --exists=build node scripts/vetolines.js build/distributions/local-developer/bin/run.bat #!
+ #squarespace/server#1.1.2
updated 1 package in 56.891s
Following that, I clone my site into a folder on my desktop from git and then navigate to the folder in terminal. At this point, I attempt to start the Dev Server, by running the following command(with the "site-name" changed to my site's name:
squarespace-server https://site-name.squarespace.com
My problem begins here, I am met with the following response from the terminal:
-bash: squarespace server: command not found
My mac doesn't recognize the server, even though I found the folder manually on my computer (but I don't know what to do with it).
So far I have attempted a couple troubleshooting methods:
I have a trial site so I tried to use the --auth flag as suggested on the documentation.
I restarted the whole process, so I removed all node and squarespace related files from my system and started again.
After looking online for answers, I installed homebrew to make sure that I am installing node and git correctly to my system.
Finally, I have attempted to change permissions for npm (but I'm not sure that I did this part correctly or not since I don't receive any permission errors).
Also, thank you so much for reading through all this. I just really wanted to make sure you all understood where I was at in this whole process.
I think you can solve this by adding an export path to your profile.
Open the terminal
Enter the following command
touch ~/.bash_profile
(this creates the bash profile)
open ~/.bash_profile
(this opens the bash profile you just created)
Your bash profile will open in a text editor.
Add the following line, then save:
export PATH=~/.npm-global/bin:$PATH
Restart terminal and try using the command again. < This part is important. If you don't restart your terminal it won't recognise the profile.
https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally
Related
I am a student who has gotten a part time job embedded system programming. I am given a program the company uses, and asked to understand it. This is a working program. Therefore, the project can be built and flashed on ESP32 by the developers with no problem. So, the code and CMake files should have no issues. However, I cannot build the program either with VSCode extension nor with idf.py. In fact, I cannot build esp-idf examples from the official website, either.
Note: I am new to StackOverflow as well as to ESP32, so sorry if I made any mistakes here. If this post is problematic in any way, please inform me.
The error message from the terminal is shown here
I was initially using VSCode on Windows 10 (Windows is not activated). At first, ESP extension was completely failing to start the building process because it could not locate the tools. I was getting "could not be located" errors for all the tools. Below is a list of what I did in this setting:
I had v5.0.0 for esp-idf downloaded from Espressif server. I deleted it and tried v4.3.3 and then I tried to download from Github server. I downloaded the requirements for idf.py scripting environment and completed the settings for it as described by the Espressif's documentation.
I manually set the environment variables for IDF_PATH and PATH for both the user and for the system.
After 2, the initial error was gone. Unfortunately, I had a new error which indicated that ".elf" file for the project output could not be found. I do not exactly recall the error but if it is integral to the problem's solution I can try to replicate this issue.
I tried to delete and reinstall VSCode. I tried running VSCode with admin authority.
I tried changing the IDF_TOOLS_PATH in the VSCode esp-idf extension configurations from ".espressif" to "esp\esp-idf".
At this point, I moved to try to build the project on Ubuntu 22.04.1 LTS:
In Ubuntu, I got the fatal error: esp_event.h: No such file or directory error.
It does not seem to be a common issue and I could not find much about it online.
I followed the Linux setup steps in the documentation. It said that only step 1 (Downloading the prerequisites) was necessary for the VSCode extension.
I decided to try the "master branch" from esp-idf configurations as well. After I downloaded the master branch, the error changed to the current version: 'fatal error: esp_wifi.h: No such file or directory'
I also tried the idf.py in Ubuntu but I got the same error.
Both in Ubuntu and in Windows, the Doctor Command returns nothing. It does not even open the terminal or any window. I am not sure what it should return but some online discussions were asking about its return so I wanted to note it here.
Edit: When I tried the examples on Ubuntu, they actually build just fine. Doctor Command also works with examples.
However, the main code has still issues. Initially, I assumed I made some mistakes with esp-idf configurations. But, perhaps that was not the case.
I had the same problem and ended up editing my project's CMakeLists.txt. When I added "esp_wifi" to the "REQUIRES" list, it worked for me:
idf_component_register(
SRCS "main.c"
INCLUDE_DIRS res
EMBED_FILES res/settings.html
REQUIRES esp_wifi
)
I have a folder on my Desktop named work where I keep all my php projects. I use MAMP and all projects are set to work on virtual hosts, for example, if I have a project named test I access this project on this URL http://test.dev.
Everything went ok until I updated to macOS Catalina when I started to have this error.
(1)Operation not permitted: Can't open directory for index: /Users/username/Desktop/work/php/development/projectname.
I set the permissions to the work folder and all subfolders to be read & write for my user and staff group, I tried all the terminal permission
commands: chmod 777, 755, etc.
I had the same problem like you, and I spent many days to solve it by doing:
stop MAMP, then open terminal and type
sudo /Applications/MAMP/bin/startApache.sh -> then Enter
and then type your admin password to give apache full privileges to start apache. (this way can let MAMP read any files on your Mac, include external drives)
now you can open MAMP and see that Apache is started, then click Start on MAMP app to start MySql too.
I've solved doing the following operations:
Quit MAMP and all the applications that are using mySql and Apache Server (stop all the instances)
Go to System Preferences, Systema & Privacy, Full Disk Access Tab
Click "add" and go to /Applications/MAMP/Library/bin and add apachectl
Run this command from the terminal: sudo /Applications/MAMP/bin/startApache.sh\
Open MAMP and press the Start Servers button
now you should be able to start your localhost app
This could be due to wrong permission given by the new MacOS Catalina permission manager. A possible way to solve this issue is to check if the folder in which the project is stored can be accessed by your Application.
To do this you have to:
Go to System Preferences
Go to System & Privacy
Go to Files and Folders
Be sure that the folder of your project is checked in the subsection concerning your Application
I hope this could solve your problem.
Prior to the steps below I added Full disk access to MAMP under the Security and Privacy Folder.
The steps I did after:
Stop MAMP
Open terminal
Then type: /Applications/MAMP/bin/startApache.sh
Start MAMP
Incase it wont work, try on the terminal: /Applications/MAMP/bin/stopApache.sh and then /Applications/MAMP/bin/startApache.sh
I had a similar problem with XAMPP. Apache just lost access to my external drive, which I included via a symlink. Even giving "Full Disk Access" to the httpd webserver didn't help.
The final solution was to start Apache with the sudo command:
sudo Applications/XAMPP/bin/apachectl start
did the job for me. Please note that
sudo apachectl start
would start the Apache that comes with macOS and thus wouldn't be used with XAMPP (and MAMP as well, I guess).
I'm trying to perform audit using Lighthouse DevTools.
My site requires authentication.
When I run the test the lighthouse logs me out and only anayses /login.
How can I get Lighthouse DevTools to analyse my site? Can I supply login credentials?
If you are using local storage in order to preserve an authenticated state after refresh
(for example storing a user's token, and on refresh using that token in order to login like a lot of SPA's)
I found a solution that might work :
https://github.com/GoogleChrome/lighthouse/issues/1418#issuecomment-397753583
If using chrome dev tools to run light house :
On the lighthouse tab in chrome dev tools simply click the settings icon
Uncheck the clear storage check box.
Generate the report, and on refresh it will use the local storage data therefore will keep you logged in.
If using the lighthouse cli tool :
Install and execute as explained in JoostS answer, just add to the lighthouse command the --disable-storage-reset flag , and you can also add the --view flag in order to open a tab for the report.
So the command will be :
lighthouse <url> --port <port_chrome_debugger_opened> --disable-storage-reset --view
Verifying it tested the logged in page
You can verify it tested the logged in page by looking at the report under the performance metrics there are images of the page that was loaded, so if the images correspond to the logged in page I believe it means it was tested correctly.
See Testing on a site with authentication in the official readme:
When installed globally via npm i -g lighthouse or yarn global add lighthouse, chrome-debug is added to your PATH. This binary launches a standalone Chrome instance with an open debugging port.
Run chrome-debug. This will log the debugging port of your Chrome instance
Navigate to your site and log in.
In a separate terminal tab, run lighthouse [siteurl] --port port-number using the port number from chrome-debug.
I had to install node 10.16.3 first (node.js > 10.0.0).
nvm install 10.16.3
will show error
Could not download npm for node v10.16.3.
Download npm version what you want - https://github.com/npm/cli/releases
I had downloaded 6.9.0 npm version - https://github.com/npm/cli/archive/v6.9.0.zip
It should be extracted to C:\Users\xxx\AppData\Roaming\nvm\v10.16.3\node_modules\npm
then go to C:\Users\xxx\AppData\Roaming\nvm\v10.16.3\node_modules\npm\bin and copy two npm files. first (npm .cmd file), second (npm file)
then paste both files in C:\Users\xxx\AppData\Roaming\nvm\v10.16.3
open cmd and run command node -v and npm -v
After that lighthouse CLI works as expected.
The command still does not work though. :/
I have followed the advice of JoostS - Testing a site with authentication
The technique does not work. It opens up an new, not logged in window, and behaves just like you would expect without the --port argument.
Edit:
Summary, I tried to follow only the steps listed in the below two links as applies to windows:
https://github.com/mapbox/mapbox-gl-js/blob/master/CONTRIBUTING.md
https://github.com/stackgl/headless-gl#windows
Here I have reattached the screenshot of the commands that I had problems with:
https://imgur.com/RCQCNU5
One more step I took that I should mention is I also did not find the headless gl when I downloaded the repository, when the install headless gl command did not work I manually copied the file and put it in my local copy under the nodemodules directory thinking it would work but it didnt solve anything. I do think this is related to access issues but I dont know what else I should try to get it working?
First, let's clarify your problem: you want a version of mapbox-gl.js which contains a recently fixed bug.
Your best option is to just wait a couple of weeks for a release.
Failing that, you should build your own, from master. You don't need to set up a debug server for that. You can skip straight to the "Creating a Standalone Build" section.
If the steps for building on Windows don't work for some reason, you could set up a local virtual machine running Ubuntu and use that.
But honestly, just wait a couple of weeks. :)
Just in case some one else need to run this on local server.
After clone
Run npm install
npm run start-debug
It will start listening on port 9966.
Test the debug html files entering to
localhost:9966/debug/FILE_NAME_TO_TEST.html
In Terminal everything is working just fine:
alex#ubuntu:~/workspace/spt$ export PATH=$PATH:/usr/lib/meteor/bin
alex#ubuntu:~/workspace/spt$ mrt
Stand back while Meteorite does its thing
Done installing smart packages
Ok, everything's ready. Here comes Meteor!
[[[[[ ~/workspace/spt ]]]]]
Running on: http://localhost:3000/
Now I want to see the output in Eclipse console, so I create "External Tools Configurations" and have:
Also I add the PATH:
However when I try to run I get the following output in console:
[1m[37mStand back while Meteorite does its thing[39m[22m
[1m[37mDone installing smart packages[39m[22m
[32mOk, everything's ready. Here comes Meteor![39m
/home/alex/.meteorite/meteors/meteor/meteor/2d8b41a87cec884489ead138b5dfea31487363f3/meteor:
line 7: uname: command not found Sorry, this OS is not supported.
Any ideas on what's going on?
I think somehow when it says Append its a loose definition. If meteor can't find uname it means path has been emptied to /usr/lib/meteor/bin. You could create a complete path variable manually:
Find out your path, run echo $PATH in your terminal, and add your :/usr/lib/meteor/bin to it and use this as your path in that dialog in the screenshot.