Open rookboom opened 7 years ago
I'll check it out and see what i can find.
Here's a quick link that may have some more info https://github.com/fable-compiler/Fable/issues/432
matt
On Sat, Jan 7, 2017 at 10:39 AM, Johan Verwey notifications@github.com wrote:
Hi,
Thanks for posting this tutorial. I am having trouble getting the watch task to work.
When I run 'task watch' from VS Code, it builds the project for the first time. But nothing happens when I modify client.fs or server.fs?
Any ideas?
Thanks Johan
Here is the output when I run the watch task:
todo-elm-fable@1.0.0 watch d:\repos\HelloArchFableSuave fable -w --target watch fable-compiler 0.7.26: Start compilation... d:\repos\HelloArchFableSuave> npm install [ERROR] npm [ERROR] WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.17: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN todo-elm-fable@1.0.0 No description npm WARN todo-elm-fable@1.0.0 No repository field. [WARNING] This expression is a function value, i.e. is missing arguments. Its type is AppMessage<Actions,string> -> unit. (L48,0-L50,8) (d:\repos\HelloArchFableSuave\src\client\client.fs) Compiled fable-arch\Fable.Arch.Html.js at 8:24:40 AM Compiled fable-arch\Fable.Arch.App.js at 8:24:40 AM Compiled fable-arch\Fable.Arch.Virtualdom.js at 8:24:40 AM Compiled client\client.js at 8:24:40 AM d:\repos\HelloArchFableSuave> webpack --watch Hash: 96a2354ab044a5037016 Version: webpack 1.14.0 Time: 631ms Asset Size Chunks Chunk Names bundle.js 351 kB 0 [emitted] main bundle.js.map 399 kB 0 [emitted] main
- 67 hidden modules WARNING in .//fable-core/umd/Symbol.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/Symbol.js 3:24-31 WARNING in .//fable-core/umd/List.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/List.js 3:24-31 WARNING in .//fable-core/umd/Util.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/Util.js 3:24-31 WARNING in .//fable-core/umd/String.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/String.js 3:24-31 WARNING in .//fable-core/umd/Array.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/Array.js 3:24-31 WARNING in .//fable-core/umd/Assert.js Critical dependencies: 8:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/Assert.js 8:24-31 WARNING in .//fable-core/umd/Async.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/Async.js 3:24-31 WARNING in .//fable-core/umd/Choice.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/Choice.js 3:24-31 WARNING in .//fable-core/umd/BitConverter.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/BitConverter.js 3:24-31 WARNING in .//fable-core/umd/AsyncBuilder.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/AsyncBuilder.js 3:24-31 WARNING in .//fable-core/umd/Event.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/Event.js 3:24-31 WARNING in .//fable-core/umd/Date.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/Date.js 3:24-31 WARNING in .//fable-core/umd/Lazy.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/Lazy.js 3:24-31 WARNING in .//fable-core/umd/GenericComparer.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/GenericComparer.js 3:24-31 WARNING in .//fable-core/umd/ListClass.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/ListClass.js 3:24-31 WARNING in .//fable-core/umd/Long.js Critical dependencies: 4:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/Long.js 4:24-31 WARNING in .//fable-core/umd/MailboxProcessor.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/MailboxProcessor.js 3:24-31 WARNING in .//fable-core/umd/Map.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/Map.js 3:24-31 WARNING in .//fable-core/umd/Observable.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/Observable.js 3:24-31 WARNING in .//fable-core/umd/RegExp.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/RegExp.js 3:24-31 WARNING in .//fable-core/umd/Reflection.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/Reflection.js 3:24-31 WARNING in .//fable-core/umd/Serialize.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/Serialize.js 3:24-31 WARNING in .//fable-core/umd/Seq.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/Seq.js 3:24-31 WARNING in .//fable-core/umd/Timer.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/Timer.js 3:24-31 WARNING in .//fable-core/umd/TimeSpan.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/TimeSpan.js 3:24-31 WARNING in .//fable-core/umd/Set.js Critical dependencies: 3:24-31 require function is used in a way in which dependencies cannot be statically extracted @ .//fable-core/umd/Set.js 3:24-31
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dogwith1eye/HelloArchFableSuave/issues/1, or mute the thread https://github.com/notifications/unsubscribe-auth/AF3wKmo07MryP-0juP-Tdn9iNXTACl15ks5rP7_CgaJpZM4LddmA .
Looks like it works when using "postbuild": "webpack" but not "postbuild": "webpack --watch"
Which is unfortunate because the webpacking is slow when not using --watch.
Hi,
Thanks for posting this tutorial. I am having trouble getting the watch task to work.
When I run 'task watch' from VS Code, it builds the project for the first time. But nothing happens when I modify client.fs or server.fs?
Any ideas?
Thanks Johan
Here is the output when I run the watch task: