Create spright-components package

[m-akinc]

Pull Request

🤨 Rationale

Resolves #1974

👩‍💻 Implementation

• Created packages/spright-components
  • has spright-accordion component with unit tests
  • README and CONTRIBUTING

Configuration includes some Storybook-related content (just to avoid having to remove and re-add later), but the actual Storybook support for spright-components will be a separate submission.

🧪 Testing

Builds and tests pass

✅ Checklist

• I have updated the project documentation to reflect my changes or determined no changes are needed.

[m-akinc]

@jattasNI Not sure it makes sense for someone other than you or Milan to buddy this, so I thought you could take an initial look before having other people review.

[rajsite]

Waiting for comments to be addressed

[rajsite]

This is not a minor change... in a published package that would mean any version of nimble-components is valid which is not accurate. You just need to get it aligned with what is the latest in main and synced to your branch. Beachball handles revving it and keeping it aligned after.

[m-akinc]

Thanks, I had been thinking of "*" as "latest", since it allows the newest version, but of course that's not what it means. Switched it back.

[rajsite]

"latest" does exist but we should use semantic version ranges to specify the version we actually test against. i.e. latest changes day-to-day and doesn't care about major versions, etc. If you want to make sure the mental model for how semver works is aligned we should discuss offline as you're setting up more packages.

[rajsite]

This came up in the wild for a third party package using wildcard specifiers for dependencies as an example: DefinitelyTyped/DefinitelyTyped#69355 (comment)

Even though the linkify-it package did a major version release to specify a breaking change users of markdown-it (directly or indirectly) were broken by the major change because markdown-it used a wildcard specifier.

[rajsite]

Needs correct package version management