| orange: #f78f2e | |
| yellow orange: #fedc0c | |
| lime green: #d1f20a | |
| pink: #fe447d | |
| emerald green: #5cd05b | |
| teal: #03c1cd | |
| blue: #0e10e6 | |
| violet: #9208e7 | |
| red orange: #f84c00 | |
| yellow: #f3f354 |
Procedure by Nevercholt Tech (https://www.youtube.com/watch?v=gVjF_MKjSv8) - transcribed by Karunamon
Note: This procedure is somewhat advanced and, if you screw up, you are likely to hard brick your switch. *Proceed with caution!
Also note that this is a full reset. All save data, installed apps, everything will be lost.
There are several ways that you can set up Node.js on a Raspberry Pi when running Raspbian/Rapberry Pi OS. Depending on your needs, the version of the RPi that you're using, and how you like to manage installs, you have a lot of options.
Do not do this if you can avoid it, it's super slow. If you insist on doing it and have the time, you can start at https://nodejs.org. But really, don't do this.
If you have tons of time on your hands, don't need Node anytime soon, and insist on building from source for some reason, here's a guide you can try out that covers building Node.js on an ARMv6 Raspberry Pi.
Side note: unless you have a need for the latest and greatest features, I recommend developing using the most recent Long Term Support (LTS) version of Node available, especially for anything you plan to put into production for any length of time.
| @echo off | |
| title Windows 10 ALL version activator&cls&echo ************************************&echo Supported products:&echo - Windows 10 Home&echo - Windows 10 Professional&echo - Windows 10 Enterprise, Enterprise LTSB&echo - Windows 10 Education&echo.&echo.&echo ************************************ &echo Windows 10 activation... | |
| cscript //nologo c:\windows\system32\slmgr.vbs /ipk TX9XD-98N7V-6WMQ6-BX7FG-H8Q99 >nul | |
| cscript //nologo c:\windows\system32\slmgr.vbs /ipk 3KHY7-WNT83-DGQKR-F7HPR-844BM >nul | |
| cscript //nologo c:\windows\system32\slmgr.vbs /ipk 7HNRX-D7KGG-3K4RQ-4WPJ4-YTDFH >nul | |
| cscript //nologo c:\windows\system32\slmgr.vbs /ipk PVMJN-6DFY6-9CCP6-7BKTT-D3WVR >nul | |
| cscript //nologo c:\windows\system32\slmgr.vbs /ipk W269N-WFGWX-YVC9B-4J6C9-T83GX >nul | |
| cscript //nologo c:\windows\system32\slmgr.vbs /ipk MH37W-N47XK-V7XM9-C7227-GCQG9 >nul | |
| cscript //nologo c:\windows\system32\slmgr.vbs /ipk NW6C2-QMPVW-D7KKK-3GKT6-VCFB2 >nul |
Short (72 chars or less) summary
More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).
Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages
| // ==UserScript== | |
| // @name Sourceforge Instant Downloader | |
| // @match *://sourceforge.net/*download* | |
| // ==/UserScript== | |
| (function() { | |
| 'use strict'; | |
| function exec(fn) { | |
| var script = document.createElement('script'); | |
| script.setAttribute('type', 'application/javascript'); |
| # | |
| # mkcd command | |
| # This is an improvised version of the mkcd command at http://superuser.com/questions/152794/is-there-a-shortcut-to-mkdir-foo-and-immediately-cd-into-it | |
| # This function has to be added to the ~/.bashrc file | |
| # After that you can run command like: mkdir abc, mkdir -p one/two/three | |
| # | |
| function mkcd { | |
| last=$(eval "echo \$$#") | |
| if [ ! -n "$last" ]; then | |
| echo "Enter a directory name" |
