profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/dyspop/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Dan Black dyspop Bangkok dan.black React n00b. Python enthusiast. Ruby lurker. Designer and musician.

dyspop/email-specifications 9

Specifications for Email Implementation

dyspop/htail 1

tail http changes via email

dyspop/amazon-ec2-user-guide 0

The open source version of the Amazon EC2 User Guide for Linux. To submit feedback or requests for changes, submit an issue or make changes and submit a pull request.

dyspop/applescripts 0

Just silly scripts for AppleScript hacking

dyspop/baywatch 0

Bayesian A/B testing as a Flask REST API

dyspop/Cerberus 0

A few simple, but solid patterns for responsive HTML email templates and newsletters. Even in Outlook and Gmail.

dyspop/common-email-responsive-breakpoints 0

A list of common HTML email responsive breakpoints

dyspop/django-colorfield 0

simple color field for models with a nice color-picker in the admin. :art:

dyspop/DLTFpT 0

Deep Learning with TensorFlow, Keras, and PyTorch

dyspop/docs 0

Documentation for Masonite

issue openedFortAwesome/Font-Awesome

v5.15 Pro license, React yarn add "Token string should not contain spaces"

Describe the bug What happened? When I yarn add @fortawesome/fontawesome-pro I get

error An unexpected error occurred: "https://npm.fontawesome.com/@fortawesome%2ffontawesome-pro: Invalid token header. Token string should not contain spaces.".
info If you think this is a bug, please open a bug report with the information provided in "/usr/src/app/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

How did you arrive here?

  1. Get valid Pro license
  2. Google "React Font Awesome Pro"
  3. Find and follow page https://fontawesome.com/v5.15/how-to-use/on-the-web/using-with/react
  4. Identify prerequisite configuration is necessary and head to https://fontawesome.com/v5.15/how-to-use/on-the-web/setup/using-package-managers
  5. Want to do per-project and with yarn and environment variables
  6. Create .npmrc in root of project (same level as package.json) with
@fortawesome:registry=https://npm.fontawesome.com/
//npm.fontawesome.com/:_authToken=${FONTAWESOME_NPM_AUTH_TOKEN}
  1. Add FONTAWESOME_NPM_AUTH_TOKEN
  2. Add to .env
FONTAWESOME_NPM_AUTH_TOKEN=XXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX npm install --save @fortawesome/fontawesome-pro
  1. enter command yarn add @fortawesome/fontawesome-pro

Note that yarn add @fortawesome/fontawesome-pro works if I put the FONTAWESOME_NPM_AUTH_TOKEN directly in the .npmrc

Version and implementation @fortawesome/fontawesome-pro@5.15.4

created time in 11 days

push eventdyspop/dyspop

Dan Black

commit sha 1970da2276c30daac7ae28176ec8df7c0f3b23be

Update README.md

view details

push time in 21 days

push eventdyspop/dyspop

Dan Black

commit sha c6ae6c17130ac310573fbfce661712324e0ca8e9

Update README.md

view details

push time in 21 days

push eventdyspop/dyspop

Dan Black

commit sha 1bbd6a93f29f0f0cf996b6a21601a9d3e3d31a89

Update README.md

view details

push time in 21 days

create barnchdyspop/dyspop

branch : main

created branch time in 21 days

created repositorydyspop/dyspop

created time in 21 days

issue commentmicrosoft/vscode

Got `Handler already set!` error when trying to undo in the editor

I had this happen by moving/renaming a folder on the host

i fixed it by doing this on Mac OS 10.15.5: https://stackoverflow.com/a/53839847/5969222

  1. Close VS Code
  2. rm -rf $HOME/Library/Application\ Support/Code
  3. rm -rf $HOME/.vscode
  4. Remove VSCode from application
  5. Reinstall VS Code
  6. Reinstall Microsoft Remote Development extension package (0.21.0 at time of writing)
eamodio

comment created time in 3 months