Add support for the dev-esp32-idf4 branch #94
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
since the error has been fixed in the nodemcu/dev-esp32-idf4 branch
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.
NodeMCU in the latest dev-esp32-idf4 branch moved file IO from the file module to the standard Lua io.
See Lua file functions moved to standard io module
This PR adds support for the dev-esp32-idf4 branch. Depending on the type of ESP, the appropriate set of commands is automatically selected.
I have tested this feature in the fork with already applied PRs
fix: upgrade prompt dep to fix non-existent property warning
Upgrade node-serialport dependency to v10 (Breaking Change)