One Paragraph of project description goes here
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
<html> | |
<body> | |
<script type="module"> | |
// Use a simple local http server like 'python3 -m http.server' | |
// Needs to liston on port 8000 | |
// Janky, but I use a local copy of the Ethers libray to avoid CORS headaches | |
// https://cdn.ethers.io/lib/ethers-5.2.esm.min.js | |
// Ethers docs: | |
// https://docs.ethers.io/v5/getting-started/ |
Mute these words in your settings here: https://twitter.com/settings/muted_keywords | |
ActivityTweet | |
generic_activity_highlights | |
generic_activity_momentsbreaking | |
RankedOrganicTweet | |
suggest_activity | |
suggest_activity_feed | |
suggest_activity_highlights | |
suggest_activity_tweet |
#!/bin/bash | |
# spotify_platform_oauth.sh | |
# | |
# A script to quickly and easily generate Spotify oauth tokens given a client | |
# id, secret, and scope. Will authenticate a user via the browser. | |
# The app must have "http://localhost:8082/' as a redirect_uri | |
# spotify_client_creds.json should contain a spotify client id and secret pair |
pkill -f "Jitouch" | |
sleep 5 | |
nohup ~/Library/PreferencePanes/Jitouch.prefPane/Contents/Resources/Jitouch.app/Contents/MacOS/Jitouch > /dev/null 2>&1 & |
#!/usr/bin/python | |
words = ['SEM', | |
'MVP', | |
'pop', | |
'DRM', | |
'ROI', | |
'DNA', | |
'SEO', | |
'flat', |
[ | |
"Aardvark", | |
"Albatross", | |
"Alligator", | |
"Alpaca", | |
"Ant", | |
"Anteater", | |
"Antelope", | |
"Ape", | |
"Armadillo", |
This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.
I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.
Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.
When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
const Article = require('../../../../app/models/article');
Those suck for maintenance and they're ugly.