writeFile not available at compile time when using the JS backend

[bogen]

in static: blocks or {.compileTime.} functions writeFile is not available with the JS backend.

$ cat writeFile.nim
static:
  "/dev/stdout".writeFile "\x1b[1;35mhello writeFile!\x1b[0m\n"

$ nim c -o:/dev/null --verbosity:0 writeFile.nim
hello writeFile!

$ nim js -o:/dev/null --verbosity:0 writeFile.nim
writeFile.nim(2, 16) Error: undeclared identifier: 'writeFile'

$ nim --version
Nim Compiler Version 0.11.2 (2015-07-15) [Linux: amd64]
Copyright (c) 2006-2015 by Andreas Rumpf

git hash: 45b6082c12dd6fc90a3dd3ca97e1ba157c3d6464

[bogen]

This issue can be worked around with staticExec:

$ cat writeFileSe.nim
import strutils

proc writeFileSe (file, text :string) {.compileTime.} =
  discard staticExec ("cat > '$1' <<-END_MARKER\n$2\nEND_MARKER\n" % [file,text])

static:
  const file = "temp.txt"
  file.writeFileSe "\x1b[1;35mhello writeFileSe!\x1b[0m\n"
  echo staticRead file

$ nim c --verbosity:0 -o:/dev/null writeFileSe.nim
hello writeFileSe!


$ nim js --verbosity:0 -o:/dev/null writeFileSe.nim
hello writeFileSe!

[dom96]

Could this be because you called your file "writeFile.nim"?

[bogen]

No. See my above example. It works with the c back end. I named it writeFile.nim because that is what I was having issues with.

But again, now with a different file name, same results.

$ cat someThingElse.nim
static:
  "/dev/stdout".writeFile "\x1b[1;35mhello writeFile!\x1b[0m\n"

$ nim c -o:/dev/null --verbosity:0 someThingElse.nim
hello writeFile!

$ nim js -o:/dev/null --verbosity:0 someThingElse.nim
someThingElse.nim(2, 16) Error: undeclared identifier: 'writeFile'

[ghost]

Still an issue

[marcolussetti]

Very new to Nim, but I seem to experience a variant of this still:

nim js -d:release -o:"a.js" "file.nim"
> undeclared identifier: 'open'

The relevant code in my file is:

var outputFile = open(targetFile, fmWrite)

Compilation to C works fine.

[alehander92]

EDIT: Nevermind, I misread and missed the compile time thing

(old comment
This would basically require supporting the node.js backend with more IO/os primitives: i've done similar stuff locally, but it seemed people are opposed to including this in the stdlib in order to motivate users to use the native backend in those cases

#7505
)

[andreaferretti]

At compile time you are not running on node

[alehander92]

@andreaferretti ah, i've completely missed that part, you're right.

very bizarre

[andreaferretti]

Works for me now