diegohaz / diegohaz/arc

require.context

Open
#131 20 comments 0 reactions 0 assignees View on GitHub
discussion help wanted
Dominant language
JavaScript
Stars
2.9k
Forks
289
PR merge metrics
No merged PRs in 30d

Description

I'm creating this issue to unify the discussions about `require.context`.

While that's very handy to import components, it comes with some drawbacks like #130, #113 and https://github.com/diegohaz/arc/issues/128#issuecomment-281914665

Personally, I don't have problems with it, the advantages are bigger than the issues for me. But, as many are having problems, we should consider removing it by default or at least give proper instructions on how to remove it.

If you are using this webpack feature (whether your project is based on ARc or not), please share your thoughts.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the linked discussions in #130, #113, and the referenced comment about require.context. Determine whether the project should remove this webpack feature by default or document how to remove it; done requires a decided direction, not just more opinions.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.