Conversation
|
@Simek just curious: why is VegaOS not in the OOT section, but in the |
Member
Author
|
Hey @pafry7, see the discussion in #1921, for more context on that. TL/DR: Vega OS is still in quite early stage, and most of the third-party package support relies on forks. Amazon folks would be working on upstreaming most of the work, when the Vega ecosystem situation is more stable, and aligned a bit more with other out-of-tree platforms, we would change the flag to be treated as platform. |
|
@Simek makes sense, thanks. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
📝 Why & how
Update entry template in README to include
vegaosfield, mention ability to provide npm package name.