Yes, but I prefer using home-manager for per application config.
So we can link the xpi file to ~/.mozilla/<Firefox-Application-ID>/<xpi-id>.xpi,
- <Firefox-Application-ID> is stored in the
application.iniin the unwrapped firefox derivation - <xpi-id> for each extension is stored in the
manifest.json, which can be retreived by extract the xpi file,
Don’t know if there is an elegant way to get the two values.
We can also store the configurations in about:config in the home.nix, then generate a corresponding user.js, start firefox with --profile <path> option and then user.js is live in <path>