jaredpalmer / jaredpalmer/react-parcel-example

Why is autoprefixer necessary for "Minimum viable React app with Parcel Bundler"?

Open
#16 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
481
Forks
57
PR merge metrics
No merged PRs in 30d

Description

As the title states, why is this module in this project? It seems like a nice-to-have, but by no means required for a React application. Could some justification be added for it's inclusion? CSS is not a concern for React applications as there are many solutions, just as there are many solutions for fetching data and organizing props. I do not see these added in this repository.

> I've included autoprefixer for vendor prefixing with the same setup as create-react-app

create-react-app ships with a ton of stuff that isn't necessary, so I'm wondering if the project aim should change or if this module should be removed.

Contributor guide

No contributing guide indexed for this repository

Research direction

Review the project's React and Parcel setup and the stated create-react-app comparison first. Resolve whether autoprefixer is required for this example or should be removed, then document the rationale or reflect the agreed dependency decision.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
build-system, frontend
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.