prettier

Current Behavior

prettier-atom is showing up as

Got this reply in an /r/react thread:

Nice. I kept looking and looking where you generate the different manifest.json files. But it looks like you used a combined one.

Be aware that there are slight differences in FF and Chrome supported extensions. So I had to keep separate manifest.json files for each browser.

The problem is that each of the browsers doesn't load the extension if

prettier

Here are 3,882 public repositories matching this topic...

prettier / prettier

prettier / eslint-config-prettier

prettier / prettier-eslint

bitjson / typescript-starter

diffplug / spotless

wesbos / eslint-config-wesbos

prettier / eslint-plugin-prettier

ladjs / lad

azz / pretty-quick

jsynowiec / node-typescript-boilerplate

prettier / vim-prettier

prettier / plugin-php

Kocal / vue-web-extension

prettier / plugin-ruby

ljlm0402 / typescript-express-starter

ModusCreateOrg / budgeting

trivago / prettier-plugin-sort-imports

sheerun / prettier-standard

jhipster / prettier-java

prettier / prettier-atom

Slow Activation Time

Current Behavior

madlabsinc / mevn-cli

manuelbieh / react-ssr-setup

dsznajder / vscode-react-javascript-snippets

Snippets missing (VSCode + Win11)

postlight / serverless-typescript-starter

aeksco / react-typescript-web-extension-starter

Update package.json scripts to define separate manifest.json files for Chrome and Firefox

Add Opera Support

Update Chrome Extension manfiest.json to V3

prettier / plugin-python

davellanedam / vue-skeleton-mvp

prettier / prettier-eslint-cli

devrsi0n / React-2048-game

tqwewe / prettier-plugin-tailwind

Improve this page

Add this topic to your repo