Publish the fork under @executor-js/emulate - #5
Merged
Conversation
The package was named 'emulate', which is owned on npm by the upstream project (ctate) and cannot be published from this fork. Our published package, and the name executor depends on, is the scoped @executor-js/emulate. Rename the package and point the release workflow at it.
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
1 participant
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.
The
emulatepackage name is owned on npm by the upstream project (ctate); this fork cannot publish to it (that is why 0.8.x never shipped). Our published package, and the name executor depends on, is the scoped@executor-js/emulate(owned by us). Renamepackages/emulateto@executor-js/emulateand point the release workflow at that name. TheemulateCLI bin name is unchanged.