Distribution.Nixpkgs.Nodejs.ResolveLockfile

Resolving a Lockfile and generating all necessary data (e.g. hashes), so that it can be converted to a nix expression. Might need IO & network access to succeed.

Documentation

resolveLockfileStatus :: ResolverConfig -> Chan Remote -> Lockfile -> IO (Either (NonEmpty Text) ResolvedLockfile)

Resolve all packages by downloading their sources if necessary.

Respects runOffline from RunConfig: If it is True, it throws an error as soon as it would need to download something which is the case for GitRemote.

data ResolverConfig

Constructors

ResolverConfig

Fields

• resolveOffline :: Bool

  If True, resolveLockfileStatus will throw an error in case resolving a hash requires network access (for when it started in a nix build)

data Resolved a

A thing whose hash is already known (“resolved”).

Only packages with known hashes are truly “locked”.

Constructors

Resolved

Fields

• hashSum :: Text
• resolved :: a

Instances

Functor Resolved

Defined in Distribution.Nixpkgs.Nodejs.ResolveLockfile

Methods

fmap :: (a -> b) -> Resolved a -> Resolved b

(<$) :: a -> Resolved b -> Resolved a

Eq a => Eq (Resolved a)

Defined in Distribution.Nixpkgs.Nodejs.ResolveLockfile

Methods

(==) :: Resolved a -> Resolved a -> Bool

(/=) :: Resolved a -> Resolved a -> Bool

Show a => Show (Resolved a)

Defined in Distribution.Nixpkgs.Nodejs.ResolveLockfile

Methods

showsPrec :: Int -> Resolved a -> ShowS

show :: Resolved a -> String

showList :: [Resolved a] -> ShowS

type ResolvedLockfile = MKMap PackageKey (Resolved Package)

In order to write a nix file, all packages need to know their shasums first.