Skip to content

Conversation

@MikeKingdom
Copy link
Collaborator

These changes replace yarn as the package manager with pnpm.

With these changes, many common dependencies can be managed in a "catalog" (defined in pnpm-workspace.yaml).

By default, pnpm is more strict and doesn't allow packages to be "hoisted" like yarn does. It's possible to configure pnpm to allow hoisting, but it's generally better to avoid it for cleaner dependencies.

One situation where hoisting is currently happening is how aries-core has a storybook whose stories refer to components in aries-site. This basically causes a circular dependency between aries-core and aries-site. Lint also currently fails on these stories with pnpm. The plan to fix this is move the examples from aries-site to aries-core so they can be exported within the workspace. aries-site will reference them from there. The storybook for them can then be moved out of aries-core to a standalone storybook in apps (where it can also reference those examples now from aries-core. This will likely be done in a follow on PR.

Deploy Preview

What does this PR do?

What are the relevant issues?

Where should the reviewer start?

How should this be manually tested?

Any background context you want to provide?

Screenshots (if appropriate)

Should this PR be mentioned in Design System updates?

Is this change backwards compatible or is it a breaking change?

@changeset-bot
Copy link

changeset-bot bot commented Nov 14, 2025

⚠️ No Changeset found

Latest commit: a011de9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@netlify
Copy link

netlify bot commented Nov 14, 2025

Deploy Preview for hpe-theme-preview ready!

Name Link
🔨 Latest commit a011de9
🔍 Latest deploy log https://app.netlify.com/projects/hpe-theme-preview/deploys/6920f23036b08a0008a95c95
😎 Deploy Preview https://deploy-preview-5545--hpe-theme-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify
Copy link

netlify bot commented Nov 14, 2025

Deploy Preview for unrivaled-bublanina-3a9bae ready!

Name Link
🔨 Latest commit a011de9
🔍 Latest deploy log https://app.netlify.com/projects/unrivaled-bublanina-3a9bae/deploys/6920f2306eb72b000870e27c
😎 Deploy Preview https://deploy-preview-5545--unrivaled-bublanina-3a9bae.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify
Copy link

netlify bot commented Nov 14, 2025

Deploy Preview for hpe-design-icons-grommet failed. Why did it fail? →

Name Link
🔨 Latest commit a011de9
🔍 Latest deploy log https://app.netlify.com/projects/hpe-design-icons-grommet/deploys/6920f230952bad00085703c4

@MikeKingdom MikeKingdom marked this pull request as ready for review November 19, 2025 19:54
})();

global.sessionStorage = mockSessionStorage;
globalThis.sessionStorage = mockSessionStorage;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was curious about this change so looked it up, adding context for other reviewers:
Screenshot 2025-11-20 at 1 19 00 PM

Comment on lines +1035 to +1036
color: global.hpe.focusIndicator.boxShadow.color, // focusBoxShadowParts[global.hpe.focusIndicator.boxShadowParts.length - 1],
size: global.hpe.focusIndicator.boxShadow.spread, // focusBoxShadowParts[focusBoxShadowParts.length - 2],
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Context for other reviewers grommet/grommet-theme-hpe#549

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the reference. This was failing and best I could tell it need to be removed

Copy link
Collaborator

@Sulaymon333 Sulaymon333 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MikeKingdom Thank you for putting this PR up. I left some few comments.

Comment on lines 42 to 43
"@types/react": "^19.1.10",
"@types/react-dom": "^19.1.7",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"@types/react": "catalog:",
"@types/react-dom": "catalog:",

Should we consider using these packages from the workspace catalogue as well since they are pretty much the same versions.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense. There's more tuning of dependencies to do over time also.

### Applying the HPE theme

Once your project is set up with ReactJS and Grommet, make sure you have the latest [grommet-theme-hpe](https://github.com/grommet/grommet-theme-hpe) theme via `npm` or `yarn`. This will help ensure that your application is aligned with the HPE Design System colors, fonts, and default component styles.
Once your project is set up with ReactJS and Grommet, make sure you have the latest [grommet-theme-hpe](https://github.com/grommet/grommet-theme-hpe) theme via `npm`, `pnpm` or `yarn`. This will help ensure that your application is aligned with the HPE Design System colors, fonts, and default component styles.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The instruction here seems unclear to me. Did we intend to say that

"make sure you have the latest HPE theme from grommet-theme-hpe theme via any of the following commands

    pnpm install grommet-theme-hpe // or 
    bun add grommet-theme-hpe // or
    yarn add grommet-theme-hpe // or
    npm install grommet-theme-hpe 

"

Instead of

make sure you have the latest grommet-theme-hpe theme via npm, pnpm or yarn.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can tune the guidance later. I'll consider that a little out of scope with this PR since it's mainly focused on our internal build

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.

4 participants