Define package exports

Open
#22,889 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
build-system, tooling

Research direction

Start by reviewing the package.json files and the dev-infra workarounds referenced in the issue. Determine which packages need exports fields and what compatibility constraints apply. Done means package exports are defined consistently and the dev-infra workarounds are no longer needed.

Written by the indexing model from the issue text.

Description

area: build & ci

This is a placeholder to track using package exports fields in package.json.

Currently, dev-infra needs to implement workarounds since all other packages use package exports.

//cc @devversion.

Dominant language
TypeScript
Stars
27k
Forks
11.8k
Avg merge
16h 35m
Merged PRs (30d)
176

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from angular/angular-cli

All issues in angular/angular-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.