Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upFable does not recognize port command during the build script #301
Comments
|
/cc @alfonsogcnunez
Am 25.02.2018 15:00 schrieb "Peter Semkin" <notifications@github.com>:
… (irrelevant: pffff, 3rd day in a row I am trying to do at least anything
with the whole SAFE stack...)
When I run the build script, things go well until this line:
dotnet fable --port free webpack-dev-server
For this I get:
Unrecognized command: --port. Use dotnet fable --help to see available
options.
App runs well at my 8080 if I remove --port free from this line in
*build.fsx*:
let fablewatch = async { runDotnet clientPath "fable --port free
webpack-dev-server" }
I am just starting with SAFE, have a little idea how things work here.
ASAIU, fable actually *does* support port option. Also I see something
<#289> has been done
around this recently. Maybe fable here is not updated to a version when it
started to support this option?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#301>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AADgNECzGXWW9qVU9kwpOHPeRpFX7LFzks5tYWeBgaJpZM4SSTe8>
.
|
Should be done until this is resolved: SAFE-Stack/SAFE-BookStore#301
|
I think the args order is wrong. It should be > dotnet fable --help
Fable F# to JS compiler (1.3.17)
Usage: dotnet fable [command] [script] [fable arguments] [-- [script arguments]]
Commands:
-h|--help Show help
--version Print version
start Start Fable daemon
npm-run Run Fable while an npm script is running
yarn-run Run Fable while a yarn script is running
node-run Run Fable while a node script is running
shell-run Run Fable while a shell script is running
webpack Start Fable daemon, invoke Webpack and shut it down
webpack-dev-server Run Fable while Webpack development server is running
Fable arguments:
--timeout Stop the daemon if timeout (ms) is reached
--port Port number (default 61225) or "free" to choose a free port
--verbose Print more info during execution
To pass arguments to the script, write them after `--`. Example:
dotnet fable npm-run build --port free -- -p --config webpack.production.js
You can use shortcuts for npm and yarn scripts in the following way:
dotnet fable yarn-start # Same as `dotnet fable yarn-run start` |
|
Please send PR. Also I assume the template might be wrong then. /cc
@theimowski
Maxime Mangel <notifications@github.com> schrieb am Fr., 13. Juli 2018,
09:48:
… I think the args order is wrong.
It should be webpack-dev-server --port free.
> dotnet fable --help
Fable F# to JS compiler (1.3.17)
Usage: dotnet fable [command] [script] [fable arguments] [-- [script arguments]]
Commands:
-h|--help Show help
--version Print version
start Start Fable daemon
npm-run Run Fable while an npm script is running
yarn-run Run Fable while a yarn script is running
node-run Run Fable while a node script is running
shell-run Run Fable while a shell script is running
webpack Start Fable daemon, invoke Webpack and shut it down
webpack-dev-server Run Fable while Webpack development server is running
Fable arguments:
--timeout Stop the daemon if timeout (ms) is reached
--port Port number (default 61225) or "free" to choose a free port
--verbose Print more info during execution
To pass arguments to the script, write them after `--`. Example:
dotnet fable npm-run build --port free -- -p --config webpack.production.js
You can use shortcuts for npm and yarn scripts in the following way:
dotnet fable yarn-start # Same as `dotnet fable yarn-run start`
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#301 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADgNJoMNZo17hD9KVMbyJR08RhOpLH1ks5uGFCxgaJpZM4SSTe8>
.
|
|
Currently template doesn't use |

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

(irrelevant: pffff, 3rd day in a row I am trying to do at least anything with the whole SAFE stack...)
When I run the build script, things go well until this line:
dotnet fable --port free webpack-dev-serverFor this I get:
Unrecognized command: --port. Use dotnet fable --help to see available options.App runs well at my 8080 if I remove
--port freefrom this line in build.fsx:let fablewatch = async { runDotnet clientPath "fable --port free webpack-dev-server" }I am just starting with SAFE, have a little idea how things work here. ASAIU, fable actually does support port option. Also I see something has been done around this recently. Maybe fable here is not updated to a version when it started to support this option?