diegohaz/arc

require.context

Open

#131 opened on Feb 24, 2017

View on GitHub
 (20 comments) (0 reactions) (0 assignees)JavaScript (291 forks)github user discovery
discussionhelp wanted

Repository metrics

Stars
 (2,924 stars)
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

Research direction
Review the pros and cons of require.context in webpack, explore alternative approaches like explicit imports or dynamic imports, and evaluate whether to remove it by default or provide migration instructions.
Tech stack
javascriptreact
Domain
frontend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
Reactwebpack
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40