WIP: Fixing fable-compiler-js when run from NPM #3795
Merged
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
… the provided path is just a filename
MangelMaxime
force-pushed
the
fix/fable-compiler-js
branch
from
7d90f26
to
8677279
Compare
|
Thanks @MangelMaxime! |
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.
#3794 #3793
How to run:
./build.sh compiler-jscd src/fable-compiler-jsnpm link @fable-org/fable-metadata ../fable-metadatanode index.jsnode index.js --versionworks butnode index.js test.fsxfails ATMTo avoid the problem with having it working locally but not when packaged, we should probably remove the compiler directives and make use of
npm linkso it behave the same locally as if published.