Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: TUP-700 @tacc/core-components - use, test, fix #465

Conversation

wesleyboar
Copy link
Member

@wesleyboar wesleyboar commented May 20, 2024

Overview

  1. Test …/core-components as @tacc/core-components in clients.
  2. Fix issues.

Related

Changes

  • fixed dependency organization
  • refactored Formik field wrappers to work from external package

Testing

0. ✅ Package @tacc/core-components

  1. npm install --include=optional --workspace=libs/core-components

  2. Build @tacc/core-components i.e.
    npx nx build core-components

  3. Package @tacc/core-components (for use in local install) e.g.
    npm pack --workspace=libs/core-components --pack-destination=../1

  4. Prepare a client to use @tacc/core-components package.

    See sections 1.A.–1.C. for status

    1. Create or Checkout branch feat/TUP-700-core-components-node-pkg--use-pkg.
    2. Delete react/src/core-components and react/src/core-wrappers.
    3. Find code references to core-components and core-wrappers.
    4. Replace imports of core-components and core-wrappers with @tacc/core-components.
    5. Remove non-import references to core-components and core-wrappers.

1.A. ✅ & ➡️ Client: TACC-Cloud/Hazmapper

Started: TACC-Cloud/hazmapper#239

  1. Set up https://github.com/TACC-Cloud/hazmapper.
  2. Verify app renders with its core-components.
  3. Checkout feat/TUP-700-core-components-node-pkg--use-pkg.
  4. npm install --save ../../tacc-core-components-0.0.1.tgz1
  5. Verify no errors.
  6. Verify app works with installed core-components.
    Feat/tup 700 core components node pkg use pkg fixes TACC-Cloud/hazmapper#272

1.B. ⏯️ Client: TACC/Core-Portal

Skipped. 2

  1. ➡️ Set up https://github.com/TACC/Core-Portal.
  2. Verify app renders with its core-components.
  3. Checkout feat/TUP-700-core-components-node-pkg--use-pkg.
  4. npm install --save ../../tacc-core-components-0.0.1.tgz1
  5. Verify no errors.
  6. Verify app works with installed core-components.

1.C. ✅ Client: TACC/tup-ui

Skipped. 2

  1. ➡️ Set up 2nd clone of https://github.com/TACC/tup-ui.
  2. Verify app renders with its core-components.
  3. Checkout feat/TUP-700-core-components-node-pkg--use-pkg.
  4. npm install --save ../../tacc-core-components-0.0.1.tgz1
  5. Verify no errors.
  6. Verify app works with installed core-components.

UI

Skipped.

Notes

Archived

[!WARNING]
Installing on client TACC-Cloud/Hazmapper causes warnings about Vite version because client's Vite version v3.0.7 is too old to be used as a peer dependency by a dev dependency of an optional dependency of @tacc/core-components.

Footnotes

  1. Tester should check paths to @tacc/core-components: to where to package, from where to install. 2 3 4

  2. Having this library work on TUP client as internal library and on Hazmapper client is enough for now. I'd like to get this PR merged because it is working on two clients and merging it allows us to move core-components to its own repo. 2

@wesleyboar wesleyboar mentioned this pull request Oct 16, 2024
2 tasks
wesleyboar and others added 2 commits October 18, 2024 11:09
* Move to peer dependencies

Also add vite for building as we want to make stand-alone

* Make 0.0.3 prelease

* Bump postcss and postcss-preset-env to match core styles requirements

* Fix pretty issue

* Add vite-plugin-lib-inject-css

* Make uuid only as a dependeny allow any 8 or 9 version

---------

Co-authored-by: Wesley B <[email protected]>
@wesleyboar wesleyboar marked this pull request as ready for review October 18, 2024 18:14
@wesleyboar wesleyboar merged commit bb8571d into epic/TUP-700-core-components-node-pkg Oct 18, 2024
1 check passed
@wesleyboar wesleyboar deleted the feat/TUP-700-core-components-node-pkg--use-pkg branch October 18, 2024 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants