Skip to content

Instantly share code, notes, and snippets.

View vkuprin's full-sized avatar
⚫
Building Site Spy

Vitaly Kuprin vkuprin

⚫
Building Site Spy
23 followers · 60 following
View GitHub Profile
@vkuprin
vkuprin / one-liner-cleanup-respecting-gitignore.sh
Last active September 8, 2025 15:56
git ls-files -c "*.js" "*.jsx" "*.ts" "*.tsx" | xargs -I{} perl -i -0pe '
# First, handle specific JSX/TSX comment blocks with curly braces
s|\{\/\*.*?\*\/\}||gs;
# Then handle regular comments
s|(?<!\:)//[^\n]*| |g;
s|/\*.*?\*/| |gs;
# Clean up extra whitespace
s|[ \t]+\n|\n|g;
' {}
@dhbloo
dhbloo / index.html
Created December 16, 2024 09:44
Example code to communicate with rapfi WASM module
<head>
<!-- Change this file name to the actual JS file name. -->
<script src="rapfi-multi.js"></script>
</head>
<body>
<input type="text" id="incommand" size="80" onkeydown="keydown()" />
<input type="button" value="SendCommand" onclick="sendCommand()" />
<input type="button" value="Terminate" onclick="terminate()" />
<br />
<textarea id="output" readonly rows="50" cols="120"> </textarea>
@Kyle-Ye
Kyle-Ye / iPhone Mirroring.md
Last active January 17, 2026 14:18
Launch iPhone Mirroring.app on macOS 15 Beta 1
@patchthecode
patchthecode / reset_idea_trial.sh
Created June 29, 2021 22:50 — forked from gulrich1/reset_idea_trial.sh
reset intellij trial
#!/bin/sh
#https://github.com/PythonicNinja/jetbrains-reset-trial-mac-osx/blob/master/runme.sh
for product in IntelliJIdea WebStorm DataGrip PhpStorm CLion PyCharm GoLand RubyMine Rider; do
echo "Closing $product"
ps aux | grep -i MacOs/$product | cut -d " " -f 5 | xargs kill -9
echo "Resetting trial period for $product"
@gulrich1
gulrich1 / reset_idea_trial.sh
Created March 22, 2021 13:46
reset intellij trial
#!/bin/sh
#https://github.com/PythonicNinja/jetbrains-reset-trial-mac-osx/blob/master/runme.sh
for product in IntelliJIdea WebStorm DataGrip PhpStorm CLion PyCharm GoLand RubyMine Rider; do
echo "Closing $product"
ps aux | grep -i MacOs/$product | cut -d " " -f 5 | xargs kill -9
echo "Resetting trial period for $product"
@gragland
gragland / use-toggle.jsx
Last active October 5, 2022 05:58
Thought process when creating a useToggle() React hook with useState
import { useState, useCallback } from "react";
function useToggle(initialValue = false){
// State with initial boolean value (true/false)
const [state, setState] = useState(initialValue);
// Let's create a toggle function
// This works, but we're using the state value from above
// instead of the current state. Usually they are the same,
// but if this hook was triggered multiple times rapidly then
@Rich-Harris
Rich-Harris / what-is-svelte.md
Last active December 27, 2025 05:32
The truth about Svelte

I've been deceiving you all. I had you believe that Svelte was a UI framework — unlike React and Vue etc, because it shifts work out of the client and into the compiler, but a framework nonetheless.

But that's not exactly accurate. In my defense, I didn't realise it myself until very recently. But with Svelte 3 around the corner, it's time to come clean about what Svelte really is.

Svelte is a language.

Specifically, Svelte is an attempt to answer a question that many people have asked, and a few have answered: what would it look like if we had a language for describing reactive user interfaces?

A few projects that have answered this question:

@osvaldasvalutis
osvaldasvalutis / service-worker-disable-file-cache-nginx
Created October 2, 2017 07:44
Service Worker gotchas – https://medium.com/kollegorna/service-worker-gotchas-af20a9dab986
server {
location ~* (serviceworker\.js)$ {
add_header 'Cache-Control' 'no-store, no-cache, must-revalidate, proxy-revalidate, max-age=0';
expires off;
proxy_no_cache 1;
}
}
@bigsergey
bigsergey / review-checklist.md
Last active January 11, 2026 19:23
Front-end Code Review Checklist

Review checklist

General

  1. Does the code work?
  2. Description of the project status is included.
  3. Code is easily understand.
  4. Code is written following the coding standarts/guidelines (React in our case).
  5. Code is in sync with existing code patterns/technologies.
  6. DRY. Is the same code duplicated more than twice?