Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Library with secondary entry points only

See original GitHub issue

Type of Issue

[ ] Bug Report
[x] Feature Request

Description

Would it be good idea for ng-packagr to support a library consisting of secondary points alone? Something like @angular/material is doing.

How To Reproduce

n/a

Expected Behaviour

@angular/material is a library that inspires a lot of other libraries, I am sure. Would it not be a good idea to support their structure?

Example:

| - library
  | - component-a
  | - component-b

Could result in @org/library/component-a and @org/library/component-b.

Version Information

n/a

Issue Analytics

State:
Created 3 years ago
Reactions:16
Comments:10 (6 by maintainers)

Top GitHub Comments

3reactions

paulayo93commented, Jun 26, 2020

Currently challenged by this issue. Is it possible to have the feature included?

1reaction

SchnWaltercommented, Jan 18, 2021

Just to add a note, we already have an undocumented support for empty “secondary entry points”, which allows us to have a library that skips “one level” in the sub-package path:

@example/package
@example/package/core
@example/package/components/badge
@example/package/components/toggle
@example/package/components/toggle/testing
@example/package/components/testing/integration

Notice the missing @example/package/components and @example/package/components/testing sub-packages, see comments on: https://github.com/ng-packagr/ng-packagr/issues/1748#issuecomment-696284548

This feature would be similar to that, if official support is added for such a feature, we should probably deal with these features in the same MR.