Skip to content

Postinstalls in nested dependencies should run before dependent shards #360

@jgaskins

Description

@jgaskins

Given this dependency structure:

  • app
    • dep-a
      • dep-b

If dep-a and dep-b both have postinstall scripts, we want dep-b's postinstall to run first since dep-a may depend on it, just as we would if we ran shards build from within in dep-a's own directory locally.

I attempted to solve with #359 but it is not a guaranteed solution — since app and dep-a could both list dep-b as a dependency separately, its placement in the flattened list of dependencies is not guaranteed.

Metadata

Metadata

Assignees

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