enhancement/issue 124 refactor handling and logging for entry points and dependencies with no custom element export
#125
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…no custom element export
thescientist13
added
documentation
thescientist13
changed the title
export
thescientist13
deleted the
enhancement/issue-124-no-custom-element-export-error-handling
branch
thescientist13
commented
Dec 27, 2023
| ` | ||
| : serialize(finalTree); | ||
| } else { | ||
| console.warn('WARNING: No custom element class found for this entry point.'); |
There was a problem hiding this comment.
In retrospect, maybe this should be more of a debug instead of warn?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue
resolves #124
Summary of Changes
initializeCustomElementrenderToStringentry point is not a custom element