[GH-ISSUE #1284] Instructions in "Setting up a dev environment" are not working #854

Closed
opened 2026-02-25 22:38:17 +03:00 by kerem · 3 comments
Owner

Originally created by @heapifyman on GitHub (Nov 12, 2022).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1284

Which version of floccus are you using?

4.17.1

Sync method

Nextcloud Bookmarks

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

No response

Which version of Nextcloud Bookmarks are you using? (if relevant)

No response

Which version of Nextcloud? (if relevant)

No response

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

Following the instructions in Setting up a dev environment results in an error when running gulp:

gulp: ../src/coroutine.cc:134: void* find_thread_id_key(void*): Assertion `thread_id_key != 0x7777' failed.
[1]    111467 IOT instruction (core dumped)  gulp

It appears to be this issue: https://github.com/laverdet/node-fibers/issues/451

Apparently, fibers is not compatible with node v16 or higher. See also https://github.com/laverdet/node-fibers#readme

Expected Behavior

Running gulp should succeed.

To Reproduce

  1. Follow the instructions in Setting up a dev environment

Debug log provided

  • I have provided a debug log file
Originally created by @heapifyman on GitHub (Nov 12, 2022). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1284 ### Which version of floccus are you using? 4.17.1 ### Sync method Nextcloud Bookmarks ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. _No response_ ### Which version of Nextcloud Bookmarks are you using? (if relevant) _No response_ ### Which version of Nextcloud? (if relevant) _No response_ ### What kind of WebDAV server are you using? (if relevant) _No response_ ### Describe the Bug Following the instructions in [Setting up a dev environment](https://github.com/floccusaddon/floccus#setting-up-a-dev-environment) results in an error when running `gulp`: ``` gulp: ../src/coroutine.cc:134: void* find_thread_id_key(void*): Assertion `thread_id_key != 0x7777' failed. [1] 111467 IOT instruction (core dumped) gulp ``` It appears to be this issue: https://github.com/laverdet/node-fibers/issues/451 Apparently, fibers is not compatible with node v16 or higher. See also https://github.com/laverdet/node-fibers#readme ### Expected Behavior Running `gulp` should succeed. ### To Reproduce 1. Follow the instructions in [Setting up a dev environment](https://github.com/floccusaddon/floccus#setting-up-a-dev-environment) ### Debug log provided - [ ] I have provided a debug log file
kerem 2026-02-25 22:38:17 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@pinpontitit commented on GitHub (Nov 13, 2022):

Yes I already spoke about that with the dev, but for an older version.
He asked me if I could rewrite the doc with my discoveries, but I always report.
I'll do it soon.

But the error you have doesnt look like those I had at the time...

Could you try something and tell me if it works ?

First, try using Node 14.17.0.

If it doesn't work, check this discussion for more steps from the creator.

If you get it to work, tell me also if using Node 14.17 was enough, or if you had to do something else that you read in the discussion I provided above (or something else you found online).

It would help me for writing the new steps on the README.md.

<!-- gh-comment-id:1312632029 --> @pinpontitit commented on GitHub (Nov 13, 2022): Yes I already spoke about that with the dev, but for an older version. He asked me if I could rewrite the doc with my discoveries, but I always report. I'll do it soon. But the error you have doesnt look like those I had at the time... Could you try something and tell me if it works ? First, try using Node 14.17.0. If it doesn't work, check this [discussion](https://github.com/floccusaddon/floccus/discussions/1178) for more steps from the creator. If you get it to work, tell me also if using Node 14.17 was enough, or if you had to do something else that you read in the discussion I provided above (or something else you found online). It would help me for writing the new steps on the README.md.
Author
Owner

@heapifyman commented on GitHub (Nov 13, 2022):

With node 14 there's an issue with package-lock versions. npm bundled with node 14 still uses package-lock version 1, node 16 switched to version 2, and the current package-lock.json file is also in that format. So you'll get a warning:

npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!

And that leads to some follow-up errors down the road.

After some tests, this is what worked in the end on a freshly cloned repo:

  1. Clone repo
  2. Install node 14, e.g. nvm install lts/fermium
  3. Delete package-lock.json: rm package-lock.json
  4. Install dependencies: npm install
  5. Build: npx gulp

But I don't think that this is a sustainable solution because node 14 will be EOL after April 2023 - see https://github.com/nodejs/release#release-schedule

Even node 16 will only be maintained until September 2023 - https://nodejs.org/en/blog/announcements/nodejs16-eol/

Something needs to be done to make this project work with the current node LTS version (18 at the moment).

<!-- gh-comment-id:1312697337 --> @heapifyman commented on GitHub (Nov 13, 2022): With node 14 there's an issue with package-lock versions. npm bundled with node 14 still uses package-lock version 1, node 16 switched to version 2, and the current `package-lock.json` file is also in that format. So you'll get a warning: ``` npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it! ``` And that leads to some follow-up errors down the road. After some tests, this is what worked in the end on a freshly cloned repo: 1. Clone repo 2. Install node 14, e.g. `nvm install lts/fermium` 3. Delete `package-lock.json`: `rm package-lock.json` 4. Install dependencies: `npm install` 5. Build: `npx gulp` But I don't think that this is a sustainable solution because node 14 will be EOL after April 2023 - see https://github.com/nodejs/release#release-schedule Even node 16 will only be maintained until September 2023 - https://nodejs.org/en/blog/announcements/nodejs16-eol/ Something needs to be done to make this project work with the current node LTS version (18 at the moment).
Author
Owner

@github-actions[bot] commented on GitHub (Nov 14, 2023):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

<!-- gh-comment-id:1809384958 --> @github-actions[bot] commented on GitHub (Nov 14, 2023): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#854
No description provided.