Netstandard 2.0, redo build.fsx, version updates #26
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
added 7 commits
May 3, 2021 20:29
|
Probably worth moving over to github workflows as well instead of using Travis/Appveyor |
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.
Updates a whole bunch of dependencies & tools.
I used the
build.fsxscript from Miniscaffold and completely overwrote what was in place. There was a lot of tooling involved in the existing script that all interacted in specific ways, and instead the new version just calls yarn to invoke scripts inwebpack.config.js, which probably better mirrors common use cases.I removed the final docs tooling targets & target dependencies because I wasn't able to get the docs to generate in some test projects - lots of things seem out of date, lots of errors relating to FSharp.Literate not being able to parse scripts, etc. I think it's better to tackle this later.
Fixes #23 and #25 (by upgrading straight to Fable 3)