Mirror of forum.nim-lang.org

7913 :: File IO for the JS backend on node

• halloleo (orginal) [2021-05-03T03:49:16+02:00] view original

  For the JS backend when running under nodejs, is there a module for File/Stream IO (maybe wrapping nodejs' FS module)?

  Sorry to ask this, maybe I overlooked something basic, but I couldn't find anything in the Nim doco about it...

---

• juancarlospaco (orginal) [2021-05-03T04:09:54+02:00] view original

  https://juancarlospaco.github.io/nodejs/nodejs/jsfs.html

---

• halloleo (orginal) [2021-05-03T04:29:43+02:00] view original

  Thanks @juancarlospaco! I'm checking it out.

---

• halloleo (orginal) [2021-05-03T04:35:25+02:00] view original

  Does your project _really need at least Nim 1.4.4? I'm running Nim 1.3.5...

---

• enthus1ast (orginal) [2021-05-03T07:58:11+02:00] view original

  You can clone it, change the nimble file (lower the nim version number) then, "nimble develop" the repo and try to import it. I guess most people just leave the minimum nim requirements as nimble generates it on the module init

---

• ynfle (orginal) [2021-05-03T08:46:57+02:00] view original

  1.3.5 is an unreleased version. All odd ones are

---

• halloleo (orginal) [2021-05-03T09:00:17+02:00] view original

  I was able to convince our DevOps to install the newest Nim! :-)

---

• ynfle (orginal) [2021-05-03T13:21:56+02:00] view original

  The newest nim is 1.5.x

---

• juancarlospaco (orginal) [2021-05-03T15:18:21+02:00] view original

  Does your project really needs Nim 1.3.5 ?. What Bug stop you from upgrading?.

---

• halloleo (orginal) [2021-05-04T03:57:30+02:00] view original

  The newest nim is 1.5.x

  The tarball from Nim's download page is 1.4.6.

---

• halloleo (orginal) [2021-05-04T04:02:18+02:00] view original

  Does your project really needs Nim 1.3.5 ?. What Bug stop you from upgrading?.

  It's not a bug, it is just that our sysadmins/devops do not like to upgrade things "unnecessarily". But as said, I managed to convince them this time. :-)

  However, I think it is a bit of a general problem in the Nim eco system that lots of packages seem to ask for the latest and greatest even if a package would run on older Nims....

---

• xigoi (orginal) [2021-05-04T09:06:07+02:00] view original

  Yes, because testing if the package works on older versions is a waste of time.

---

• Araq (orginal) [2021-05-04T11:22:39+02:00] view original

  It's not a bug, it is just that our sysadmins/devops do not like to upgrade things "unnecessarily".

  The question is why the devop decided to give you 1.3.5 to begin with -- something which is not a release.

---

• ynfle (orginal) [2021-05-04T23:38:05+02:00] view original

  It's confusing for people that aren't familiar with nim that odd numbers aren't releases

---