Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Library imports #16340

Merged
merged 2 commits into from
Dec 3, 2019
Merged

Library imports #16340

merged 2 commits into from
Dec 3, 2019

Conversation

alan-agius4
Copy link
Collaborator

@alan-agius4 alan-agius4 commented Dec 3, 2019

  • Currently the library schematic doesn't support adding a secondary entry-point and having deep imports is not recommanded.

It's best if paths are more stricter when having a secondary entry-point instead of a wildcard.

Instead of :

"lib/*": [
  "dist/lib/*"
]

Users should configure:

"lib/secondary": [
  "dist/lib/secondary"
]

This would allow a better DX experience when using auto imports in IDE's.

Closes: #15952

@alan-agius4 alan-agius4 added the target: patch This PR is targeted for the next patch release label Dec 3, 2019
Copy link
Member

@clydin clydin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we consider the outDir being changed to “dist” instead of the excludes?

@alan-agius4
Copy link
Collaborator Author

@clydin let's do that

Currently the library schematic doesn't support adding a secondary entry-point and having deep imports is not recommanded.

It's best if paths are more stricter when having a secondary entry-point instead of a wildcard.

Instead of :
```
"lib/*": [
  "dist/lib/*"
]
```

Users should configure:
```
"lib/secondary": [
  "dist/lib/secondary"
]
```

This would allow a better DX experience when using auto imports in IDE's.

Closes: #15952
@mgechev mgechev merged commit 2ce4c42 into angular:master Dec 3, 2019
@alan-agius4 alan-agius4 deleted the library-imports branch December 4, 2019 06:31
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jan 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Each build of an Angular library is missing random files in the output folder
5 participants