You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
This should resolve the related bug when attempting to install the @analogjs/vitest-angular package.
Does this PR introduce a breaking change?
Yes
No
Other information
I'm not 100% certain how to test this fix myself, but GPT-4o tells me this is new pattern should satisfy the correct versioning conventions that would enable the package to be properly installed.
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Which package are you modifying?
What is the current behavior?
Closes #1112
What is the new behavior?
This should resolve the related bug when attempting to install the
@analogjs/vitest-angular
package.Does this PR introduce a breaking change?
Other information
I'm not 100% certain how to test this fix myself, but GPT-4o tells me this is new pattern should satisfy the correct versioning conventions that would enable the package to be properly installed.