Update for bindgen 0.2.93, deprecating cargo-screeps #533
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
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.
As of 0.2.93, the wasm-bindgen generated code for string enums uses the
??operator, which does not parse on node 10/12.I'm proposing deprecating cargo-screeps (at least for use with world; arena still using it for the moment) and moving to javascript-based tooling:
rollupfor bundlingbabelas a rollup plugin providing the necessary translation layernode-screeps-apifor communication with server APIThis will necessitate installing
npmand node packages in order to work with a rust bot, as well ascargo- this isn't ideal, but the breadth of tooling we'd need to maintain to continue to keep the toolchain completely native has become too much to keep up with. This allows us to keep things more easily maintained going forward.