Snippets

fakjeijchchmicjllnabpdkclfkpbiag

Create and edit JavaScript code snippets, which are synced to all your computers

Latest reviews

• (2021-02-01) Jianwu Chen: Love it. works great
• (2020-07-08) Addison Moore: Awesome extension! Just lost all my snippets from Chrome on my old computer. Wish I'd had this before. Reading through some of the older reviews it seems these issues have been fixed (Github integration, ES6 linting).
• (2020-02-23) Kamil Kriho: Super. Konecne nieco, kde sa scripty automaticky zdielaju medzi zariadeniami.
• (2020-01-28) Jarrod Whitley: Might be cool if it worked... When I try to save my token I get the error "Failed to load snippets. The gist ID xxxxxxxxxxxxx doesn't seem to exist. I've tried multiple times with different tokens. No dice, oh well.
• (2019-11-03) SORE THUMB DEV: A great replacement to the jsShell extension. It's core feature (to me) is similar to something I was already working on - a jsShell extension that synced with your Google account data -- only BETTER. I like the idea of the Gist for sharing and just generally usability amongst developers. Nicely done! ** ...but, yes, would be nice to change Theme elements (i.e. font size in the editor, Snippet List, etc.) ;) I created a pull request with a simple font-size option in the settings.
• (2018-05-08) Owen Roe: Was great before they added GitHub integration. Now they've completely gimped it. Uninstalled.
• (2018-02-21) Andrew Taylor: I really like this extension - it does what the native Chrome snippets should do. But I hope the UI gets a few changes. Mainly if the only way to run snippets will be from their kebab menu by the name it's too easy to accidentally click 'delete' and there's no confirmation and no way to undelete. I was just bit by this and it seems like there has to be a better way.
• (2017-08-08) Gerbeck S.: If you want this to be useful, disable the linter because it doesn't understand ES6 correctly. It also tried to enforce semicolons which is a sin. The other way that the linter cripples this extension is that it doesn't sync snippets that don't pass the linter--again--the linter itself is wrong. ES6 is standard in Chrome and even supports async/await.