tpope

Stars and mentions

Last 30 days, Oct 4 – Nov 2

GitHub stars15
mentions1
01234Oct 4Oct 18Nov 2
UTC days · repositories tpope owns6 repositories

Package downloads

No package download history available yet.

Top repositories

tpope’s repositories ranked by new stars, as on trending.

Loading

Contributes to

Repositories outside tpope’s account where tpope opened or reviewed pull requests in the past 365 days.

Who noticed tpope

Everyone who starred or forked tpope’s repositories since the archive began in 2011.

Notable accounts

Ordered by the stars their own repositories have received.

Biggest fans

Accounts that starred the most of these repositories.

Breakout weeks

Each repository’s best week of new stars, with the release published around it.

Mentions

1post
Nov 30 posts
  1. Typescript errors into vim quickfix You may use LSP and lua vim.diagnostic.setloclist() to show Typescript errors for a specific buffer. But sometimes you could have errors across the whole project. You can run tsc in the terminal and manually search for files with errors. But we can do better. Vim has the :make command which executes the program that is set into makeprg. By default, it's make but we can change it to any terminal program/command. The output of makeprg is then populated into quickfix. Update 🖊️ After discussion on reddit someone suggested a better approach. The error is already parced in compiler tsc. I just change makeprg=npx\ tsc instead of makeprg=tsc. vim.cmd [[ augroup strdr4605 autocmd FileType typescript,typescriptreact compiler tsc | setlocal makeprg=npx\ tsc augroup END ]] Initial post Let's create an auto command that will set makeprg to tsc if we are in a typescript project: vim.cmd [[ augroup strdr4605 autocmd FileType typescript,typescriptreact set makeprg=./node_modules/.bin/tsc augroup END ]] or with lua API: local augroup = vim.api.nvim_create_augroup("strdr4605", { clear = true }) vim.api.nvim_create_autocmd("FileType", { pattern = "typescript,typescriptreact", group = augroup, command = "compiler tsc | setlocal makeprg=npx\\ tsc", }) Run :make and see the output: :!./node_modules/.bin/tsc 2>&1| tee /var/folders/3w/m_v388s15pq9rpgswbt131w00000gn/T/nvim.strdr4605/708JAY/2 components/Date.tsx(6,28): error TS2339: Property 'toISOString' does not exist on type 'number'. (1 of 1): components/Date.tsx(6,28): error TS2339: Property 'toISOString' does not exist on type 'number'. Press ENTER or type command to continue and open the quickfix, :copen: components/Date.tsx(6,28): error TS2339: Property 'toISOString' does not exist on type 'number'. When trying to navigate to any file from quickfix, I see this error: Buffer not found. Why? Because the tsc compiler outputs in a format that is not clear for vim quickfix. The problem is in parenthesis around the file line and column: components/Date.tsx(6,28): But we can change this by piping the tsc output to sed command and replacing (6,28) with :6:28:. This is the output if we run it in the terminal: ./node_modules/.bin/tsc | sed 's/(\(.*\),\(.*\)):/:\1:\2:/' 130 ↵ components/Date.tsx:6:28: error TS2339: Property 'toISOString' does not exist on type 'number'. But to make it work in vim, we need to escape some chars. The final result is: vim.cmd [[ augroup strdr4605 autocmd FileType typescript,typescriptreact set makeprg=./node_modules/.bin/tsc\ \\\|\ sed\ 's/(\\(.*\\),\\(.*\\)):/:\\1:\\2:/' augroup END ]] Now when running :make the quickfix list is populated correctly and vim navigates to the first file in the list. I can fix Typescript errors one by one, by navigating with :cnext or using vim-unimpaired.

Trending awards, every completed day and week
Gold
21st place finishes
Silver
02nd place finishes
Bronze
03rd place finishes
Awarded repositories
1Owned by tpope now

Repositories

Ordered by gold, then silver, then bronze.

  1. heroku-fucking-consoleBest: 1st by stars, 216 stars200

Every award

Top-three finishes of these repositories in completed trending days and weeks, newest first.

  1. #1 by starsDaily trending
    92 stars
    heroku-fucking-console
  2. #1 by starsDaily trending
    216 stars
    heroku-fucking-console

A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.