whatisgithub

What is core?

gaearon/core — explained in plain English

Analysis updated 2026-07-17 · repo last pushed 2016-12-05

3JavaScriptAudience · researcherComplexity · 3/5DormantSetup · easy

In one sentence

An obsolete shared JavaScript library that once powered webpack's loader and source map handling, now superseded by later webpack versions.

Mindmap

mindmap
  root((repo))
    What it does
      Shared webpack core
      Loader management
      Source map support
    Tech stack
      JavaScript
    Use cases
      Study webpack history
      Explore old codebases
    Audience
      Developers
      Researchers
    Setup
      Not for new projects
      Historical only

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Explore how early webpack versions structured shared loader and source map logic.

USE CASE 2

Study legacy codebases that depended on webpack-core or enhanced-require.

USE CASE 3

Understand the historical evolution of webpack's internal architecture.

What is it built with?

JavaScript

How does it compare?

gaearon/coreamarjitjim/browserpilotandershaig/cssess
Stars333
LanguageJavaScriptJavaScriptJavaScript
Last pushed2016-12-052011-08-19
MaintenanceDormantDormant
Setup difficultyeasymoderateeasy
Complexity3/53/51/5
Audienceresearcherdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Obsolete, not used by webpack 2 and later, kept only for historical reference.

So what is it?

This is an obsolete shared library that once powered parts of webpack, a popular JavaScript bundling tool. The README warns upfront that it's no longer used, webpack 2 and later versions moved away from this code, so it's mainly of historical interest now. Back when it was active, webpack-core served as a foundation that multiple webpack-related tools could build on top of. Think of it like a shared toolkit: instead of webpack and a companion tool called enhanced-require each writing their own code to handle the same tasks, they both used this common core. The core handled two main technical areas: managing "loaders" (which are plugins that tell webpack how to process different file types like CSS or images) and source maps (which let developers see their original code when debugging, even though the browser is running a bundled version). The README notes it was never designed to be used on its own, it was always meant as internal infrastructure for other projects. Because webpack evolved and became more complex, the maintainers eventually decided to redesign how these pieces fit together, making this shared core unnecessary. For someone exploring webpack's history or old codebases built on early versions of webpack, this repo shows how the project was structured years ago. But for anyone starting a new project today, there's no reason to use it.

Copy-paste prompts

Prompt 1
Explain how this old webpack-core library handled loaders and source maps before webpack redesigned things.
Prompt 2
Walk me through this repo's code to understand early webpack architecture for a history deep-dive.
Prompt 3
How did enhanced-require and webpack share this core, and why was it eventually removed?
Prompt 4
What changed in webpack 2+ that made this shared core unnecessary?

Frequently asked questions

What is core?

An obsolete shared JavaScript library that once powered webpack's loader and source map handling, now superseded by later webpack versions.

What language is core written in?

Mainly JavaScript. The stack also includes JavaScript.

Is core actively maintained?

Dormant — no commits in 2+ years (last push 2016-12-05).

How hard is core to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is core for?

Mainly researcher.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.