Skip to content

Migrate to Spago v1 #315

Description

@pete-murphy

Client is on legacy Spago (v0.20.9).

From briefly looking into migrating to latest Spago, there's an apparent obstacle in that the NPM scripts rely on legacy --path to include either the dev or prod version of the Try.Config.purs module.

  -p,--path PATH           Source path to include (in addition to paths in
                           spago.dhall)

I'm not seeing a direct replacement for --path in Spago v1. The alternatives that come to mind:

  1. Add a step to each script that copies the correct Try.Config.purs into src before bundling (and add src/Try.Config.purs to .gitignore).
  2. Separate packages for -dev and -prod (each containing only Try.Config module in src) with shared dependency on what's currently in the top-level package.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions