github / github/prettier-config

Use WebComponents instead of React to remain Lite?

Open
#23 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Dockerfile
Stars
37
Forks
15
PR merge metrics
No merged PRs in 30d

Description

We already have a 256MB black hole in node_modules... This is the perfect time and decide to make something special...

![Screenshot 2023-06-06 22 17 04](https://github.com/github/prettier-config/assets/876076/b51a7c8a-d79a-434b-9d3e-f95684b1d304)

Rather than a making another clone/fork of VSCode that's worse in every way than this VSCode.dev extension by Tomáš Wróbel, or CloudFlow

![Screenshot 2023-06-06 22 18 25](https://github.com/github/prettier-config/assets/876076/8a5ecca1-9a4b-4cdc-ad83-788715c80652)

I'm thinking of something like this, but with TSX
https://stackblitz.com/edit/movies-web-components-dbapmu?file=src%2Fcomponents%2FLayout%2FLayout.ts

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the referenced StackBlitz example, especially src/components/Layout/Layout.ts, and compare its Web Components approach with the repository's current configuration and dependencies. The issue does not identify implementation files, acceptance criteria, or a defined scope, so the desired outcome would need to be agreed before work begins.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.