Repository navigation
Fall back to spago.dhall files for packages without a bower.json #218
Description
Some packages are in the PureScript registry and do not have bower.json files, but do have spago.dhall files sufficient for producing a valid Manifest. One example is halogen-hooks:
https://github.com/thomashoneyman/purescript-halogen-hooks/tree/v0.5.0
This repository doesn't have a bower.json file, but it does have a spago.dhall file that is sufficient for producing a manifest:
https://github.com/thomashoneyman/purescript-halogen-hooks/blob/v0.5.0/spago.dhall
I'm proposing that, when we find a package that has a Spago file but not a Bower file, we attempt to either:
- parse the
spago.dhallfile to get the package license and dependencies - generate a
bower.jsonfile from thespago.dhallfile, and then import the Bower file as usual
Activity
thomashoneyman commentedon Sep 16, 2021
As discussed briefly with @JordanMartinez on Discord, we may have to do some tweaking of files to make this work. For example:
packages.dhallfile too, not just thespago.dhallfilemetadata.versionin thepackages.dhallto match whatever version of Spago is being used to run the script (or to some fixed 0.14-compatible version)licensekey (see Parse LICENSE file if no license is listed in the Bowerfile #220), or setting the repository key if none is set in the Spago file.Or...rather than generating a
bower.jsonfile, maybe we just try to pull out thelicensekey and rely on the output ofspago ls depsfor the list of project dependencies at specific versions?@f-f, would
spago ls depsbe a reliable way to get the package dependencies? Or isspago bump-versiona better move?