Iron:router Meteor 3.0

I am migrating a large app to meteor 3.0.

As mentioned here : Trouble updating to 3.0-alpha.17 (minisat) - #18 by dokithonon , I am starting to add one package one by one to see if they are compatible with meteor 3.0

I encounter a problem with iron:router.
Out of the bug there was a lot of conflict of version. I downloaded them locally from atmosphere, remove the @… version constraints and I was able to update to Meteor 3.0.

But iron:router is reporting an error :

W20231223-15:04:35.701(1)? (STDERR) packages/core-runtime.js:205
W20231223-15:04:35.712(1)? (STDERR)             throw error;
W20231223-15:04:35.712(1)? (STDERR)             ^
W20231223-15:04:35.712(1)? (STDERR) 
W20231223-15:04:35.712(1)? (STDERR) Error: Cannot find module "fibers"
W20231223-15:04:35.712(1)? (STDERR)     at Object.require (/Users/dokithonon/rationalk/.meteor/local/build/programs/server/boot.js:261:26)
W20231223-15:04:35.712(1)? (STDERR)     at packages/iron_router.js:292:17
W20231223-15:04:35.712(1)? (STDERR)     at packages/iron_router.js:360:4
W20231223-15:04:35.713(1)? (STDERR)     at load (packages/core-runtime.js:139:16)
W20231223-15:04:35.713(1)? (STDERR)     at onDepLoaded (packages/core-runtime.js:118:7)
W20231223-15:04:35.714(1)? (STDERR)     at packages/core-runtime.js:153:7
W20231223-15:04:35.714(1)? (STDERR)     at Array.forEach (<anonymous>)
W20231223-15:04:35.715(1)? (STDERR)     at packages/core-runtime.js:152:22
W20231223-15:04:35.715(1)? (STDERR)     at evaluateNextModule (packages/core-runtime.js:179:14)
W20231223-15:04:35.715(1)? (STDERR)     at packages/core-runtime.js:194:9
W20231223-15:04:35.716(1)? (STDERR) 
W20231223-15:04:35.716(1)? (STDERR) Node.js v20.9.0
=> Exited with code: 1
=> Your application is crashing. Waiting for file change.

Fibers seems to be used only at 1 place

Is there a plan to update iron:router so that we can use it with meteor 3.0 ?

You can take over the maintenance and add yourself as the owner for the migration

Hi Harry,
I am definitely not capable of doing such programming…
I am actually evaluating the amount of work migrating to ostrio:flow-router-extra but this is not guarantee that this will work with Meteor 3.0 neither

No pressure man, if it’s less work for you to migrate to ostrio:flow-router-extra absolutely go for it. I just wanted to point out the migration effort as it’s crucial for us to get every helping hand we could.