tvl-depot/boilerplate/typescript/default.nix

{ pkgs, ... }:

pkgs.stdenv.mkDerivation {
  name = "typescript";
  srcs = ./.;
  buildInputs = with pkgs; [
    nodejs
    # Exposes lscpu for parcel.js
    utillinux
  ];
  # parcel.js needs number of CPUs
  PARCEL_WORKERS = "1";
  buildPhase = ''
    npx parcel build src/index.html --public-url ./
  '';
  installPhase = ''
    mv dist $out
  '';
}
Debug typescript/default.nix TL;DR - Change derivation name - Point to $src/index.html instead of non-existent index.html - Prefer defining pkgs as a function argument 2020-03-25 17:47:30 +01:00			`{ pkgs, ... }:`

			`pkgs.stdenv.mkDerivation {`
			`name = "typescript";`
Support boilerplate for TypeScript projects I would like to support boilerplate code for ReasonML, TypeScript, ClojureScript, and Elm projects before I specialize in any of these frameworks. All of my projects should use TailwindCSS. All of this boilerplate should offer: - Same command to start developing - Same API to build and deploy - TailwindCSS support - Basic boilerplate for components, state, and routes This TypeScript boilerplate is not complete, but I would like to commit the progress in case I do not return to this for awhile. 2020-03-23 23:12:18 +01:00			`srcs = ./.;`
			`buildInputs = with pkgs; [`
			`nodejs`
			`# Exposes lscpu for parcel.js`
			`utillinux`
			`];`
			`# parcel.js needs number of CPUs`
			`PARCEL_WORKERS = "1";`
			`buildPhase = ''`
Use Parcel's --public-url option when building By default Parcel prefixes output paths with /. So when Chrome loads wpcarro.dev/goals it attempts to get the CSS and JS and other assets from wpcarro.dev/ instead of wpcarro.dev/goals/. Using the --public-url ./ option makes Parcel output relative paths, which should work better for my needs. 2020-03-25 18:18:51 +01:00			`npx parcel build src/index.html --public-url ./`
Support boilerplate for TypeScript projects I would like to support boilerplate code for ReasonML, TypeScript, ClojureScript, and Elm projects before I specialize in any of these frameworks. All of my projects should use TailwindCSS. All of this boilerplate should offer: - Same command to start developing - Same API to build and deploy - TailwindCSS support - Basic boilerplate for components, state, and routes This TypeScript boilerplate is not complete, but I would like to commit the progress in case I do not return to this for awhile. 2020-03-23 23:12:18 +01:00			`'';`
			`installPhase = ''`
			`mv dist $out`
			`'';`
			`}`