Details
-
Task
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
None
Description
Various issues have cropped up recently involving dependency discrepancies between dev and CI, and with talk of possibly breaking out stripes-core into smaller packages, we may want to simplify how we consume Stripes modules as a whole.
Suggestion: Publish and version a "stripes-framework" package that wraps versions of our various "stripes-*" modules together. For example, something like:
stripes-components stripes-smart-components stripes-connect stripes-form stripes-util stripes-core stripes-core-core stripes-core-core-core etc.
This idea overlaps partly with that of the monorepo discussion which comes up from time to time. However, the difference here is, whether maintained as a monorepo or not, we would publish and dogfood (at the app/platform level) a single package, "stripes-framework".
TestRail: Results
Attachments
Issue Links
- is blocked by
-
STRIPES-544 Understand all the stripes-building scenarios, and their implications for dependency management
-
- Closed
-
- relates to
-
FOLIO-1335 document the differences between dev, CI environments
-
- Closed
-
-
STCLI-87 Make stripes-cli aware of stripes framework
-
- Closed
-
-
STRIPES-561 Release v1.0.0 of stripes framework
-
- Closed
-
-
FOLIO-1338 Regression tests fail consistently in PRs
-
- Closed
-
-
FOLIO-1450 Revise FOLIO release and deployment process
-
- Open
-
-
FOLIO-1547 Upgrade platform-core to stripes 1.0
-
- Closed
-
-
STCOM-335 SPIKE: Alternatives to React Context
-
- Closed
-
-
STRIPES-503 CONSIDER moving all Stripes libraries into a monorepo
-
- Closed
-
-
UXPROD-1058 Nightly builds and integration testing pt 1
-
- Closed
-
-
UXPROD-1156 Re-organization of the CI/CD environments and dev boxes
-
- Closed
-
-
UXPROD-1424 Re-organization of the CI/CD environments and dev boxes pt 2
-
- Closed
-