How can this be a firefox fork yet so different from upstream ?

[bacloud22]

Even source structure is so different from gecko-dev ?
Am I missing something ? or this is a different build process ?

[CutterKnife]

@nyanrus it might be your turn 👀

[nyanrus]

@bacloud22 You would check https://github.com/f3liz-dev/noraneko/blob/rftr-bridge/.github/assets/readme/noraneko.structure.light.excalidraw.svg
Floorp is currently using artifact-based developing, https://github.com/Floorp-Projects/Floorp-runtime is gecko-dev based and builds binary.
And this repository get the binary from it, and modifies with patch, injecting, placing vite results. :3
If you have any questions, feel free to call me!

[bacloud22]

this is interesting! I knew about artifact-based but didn't know it is as effective, I thought it's just "some tiny" dependencies that are not
part of the core which could be fetched without code

thank you for clarifying !