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

[FIX] Bundling: Detect manifest.json dependency of Components / Libraries #924

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

matz3
Copy link
Member

@matz3 matz3 commented Jul 14, 2023

No description provided.

@codeworrior codeworrior requested review from Thodd and codeworrior July 14, 2023 08:02
@@ -54,6 +54,7 @@ class ComponentAnalyzer {
try {
const manifestResource = await this._pool.findResource(manifestName).catch(() => null);
if ( manifestResource ) {
info.addDependency(manifestName);
Copy link
Member

Choose a reason for hiding this comment

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

I think we need to discuss whether the existence of a manifest.json should be the indicator or the manifest: json entry in the metadata or both.

  • If a manifest.json exists, manifest-first would work even if the component does not have the metadata entry
  • if the metadata entry exists, a manifest.json would be requested even if it doesn't exist

Copy link
Member Author

Choose a reason for hiding this comment

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

I agree. My idea was to always add the dependency because currently the manifest.json is always taken into account for dependency analysis.

I suggest to merge this change as-is and to follow-up on the ComponentAnalyzer as a whole, which also seems to lack detection of new features (e.g. in routing).

Copy link
Member Author

Choose a reason for hiding this comment

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

I've created #954 which only covers libraries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants