jamiebuilds

Multiple GitHub accounts (Work vs Personal)

This setup uses some tricks to ensure that the right email/name/ssh-key is used for the right repos without having to think about it ever again.

• First generate two SSH keys, ~/.ssh/id_ed25519 and ~/.ssh/id_ed25519_work
• Add one key to your personal account and the other to your work account

.ssh/config

sindresorhus

Pure ESM package

The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

1. Use ESM yourself. (preferred)
   Use import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.
2. If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
3. Stay on the existing version of the package until you can move to ESM.

mzabriskie

1. npm test
2. npm run build
3. Update package.json & bower.json version
4. Update Changelog.md
5. git commit -am"Releasing x.x.x"
6. git push
7. git tag -a vx.x.x -m"version x.x.x"
8. git push origin --tags
9. npm publish ./

tsiege

ANNOUNCEMENT

I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!






\