forked from fedimint/ui
-
Notifications
You must be signed in to change notification settings - Fork 0
/
flake.nix
102 lines (91 loc) · 3.69 KB
/
flake.nix
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
{
inputs = {
flake-utils.url = "github:numtide/flake-utils";
fedimint.url =
"github:fedimint/fedimint?rev=e147b5695abce6eeeb984974d48d562b2bf1dfe1";
};
outputs = { self, flake-utils, fedimint }:
flake-utils.lib.eachDefaultSystem (system:
let
nixpkgs = fedimint.inputs.nixpkgs;
pkgs = import nixpkgs {
inherit system;
overlays = [ fedimint.overlays.all ];
};
fmLib = fedimint.lib.${system};
# When `yarn.lock` changes, follow these steps to update the `sha256` hash:
# 1. Remove the existing `sha256` hash.
# 2. Rebuild the Nix derivation by executing:
# nix build .#guardian-ui
# 3. Obtain the new `sha256` hash from the build error message.
# 4. Update the `sha256` value below with the newly copied hash.
#
# **Important:**
# Keeping the `sha256` hash in sync with `yarn.lock` is essential. An outdated or incorrect hash
# will cause the Nix package to become out-of-sync with Yarn dependencies, potentially leading
# to build failures or inconsistent behavior.
yarnOfflineCache = pkgs.fetchYarnDeps {
yarnLock = ./yarn.lock;
hash = "sha256-a1YeZYvxstAqDCgK2qrlylkKYhIX1Xo28tCKt46hxrE=";
};
in
{
devShells = fmLib.devShells // {
default = fmLib.devShells.default.overrideAttrs (prev: {
nativeBuildInputs = [
pkgs.mprocs
pkgs.nodejs
pkgs.yarn
fedimint.packages.${system}.devimint
fedimint.packages.${system}.gateway-pkgs
fedimint.packages.${system}.fedimint-pkgs
] ++ prev.nativeBuildInputs;
shellHook = ''
yarn install
'';
});
};
packages.guardian-ui = pkgs.stdenv.mkDerivation {
pname = "guardian-ui";
version = "0.4.3";
src = ./.;
nativeBuildInputs = with pkgs; [
nodejs
yarn
cacert
yarn2nix-moretea.fixup_yarn_lock
nodePackages.serve
];
configurePhase = ''
export HOME=$(mktemp -d)
'';
# NixOS is introducing `yarnBuildHook`, `yarnConfigHook`, and `yarnInstallHook`,
# which could simplify the current complex `buildPhase` that uses `fixup_yarn_lock`
# and the `installPhase`.
# 1. [JavaScript Frameworks Documentation](https://github.com/NixOS/nixpkgs/blob/ab4dc6ca78809a367aba6fb2813a15116560e2a9/doc/languages-frameworks/javascript.section.md)
# 2. [Nixpkgs Issue #324246](https://github.com/NixOS/nixpkgs/issues/324246)
#
# Additionally, avoid using `pkgs.mkYarnPackage` as it is slated for deprecation.
buildPhase = ''
yarn config --offline set yarn-offline-mirror ${yarnOfflineCache}
fixup_yarn_lock yarn.lock
yarn install --offline \
--frozen-lockfile \
--ignore-engines --ignore-scripts
patchShebangs .
yarn build
'';
# should be similar to the installer in the Dockerfile
installPhase = ''
mkdir -p $out
# static files that can be served by reverse-proxies
cp -r apps/router/build/* $out
# wrapper for "nix run .#guardian-ui" (based on https://wiki.nixos.org/wiki/Node.js#Packaging_with_yarn2nix)
mkdir -p $out/bin
echo "#!/bin/sh" > $out/bin/guardian-ui
echo "exec ${pkgs.nodePackages.serve}/bin/serve -s $out" >> $out/bin/guardian-ui
chmod +x $out/bin/guardian-ui
'';
};
});
}