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

Add semantic-release and update build #490

Closed
wants to merge 2 commits into from

Conversation

andresriveratoro
Copy link
Contributor

@andresriveratoro andresriveratoro commented Jul 20, 2022

Chromatic

https://1021-token-library--60f9b557105290003b387cd5.chromatic.com

Description

Closes department-of-veterans-affairs/vets-design-system-documentation#1021

Acceptance criteria

  • Create a package for the design token library and publish it to NPM

Definition of done

  • Documentation has been updated, if applicable
  • A link has been provided to the originating GitHub issue (or connected to it via ZenHub)

@andresriveratoro andresriveratoro added the ignore-for-release Used if you want to ignore the PR in the generated release notes label Jul 20, 2022
@andresriveratoro andresriveratoro requested a review from a team as a code owner July 20, 2022 12:26
@@ -3,7 +3,7 @@
"platforms": {
"css": {
"transformGroup": "css",
"buildPath": "src/tokens/",
"buildPath": "dist/",
Copy link
Contributor

Choose a reason for hiding this comment

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

This would publish all of our CSS in this directory as well, correct?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Our build command "sass --load-path=../../node_modules/@uswds/uswds/packages/ src/stylesheets:dist/" takes care of this work. This buildPath change only affects tokens outputted as CSS variables.

@@ -1,9 +1,10 @@
{
"name": "@department-of-veterans-affairs/css-library",
"private": true,
"description": "VA.gov CSS library",
"version": "1.0.0",
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we publish it as 0.0.1 or something instead of a 1.0?

@@ -1,9 +1,10 @@
{
"name": "@department-of-veterans-affairs/css-library",
"private": true,
"description": "VA.gov CSS library",
Copy link
Contributor

Choose a reason for hiding this comment

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

We may also want to include Design System in there.

package.json Outdated
@@ -18,7 +18,14 @@
"trim": "^0.0.3",
"prism": "^1.27.0"
},
"scripts": {
"semantic-release": "yarn workspaces run semantic-release -e semantic-release-monorepo"
Copy link
Contributor

Choose a reason for hiding this comment

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

If we run yarn semantic-release, what will happen?

@andresriveratoro andresriveratoro marked this pull request as draft July 21, 2022 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ignore-for-release Used if you want to ignore the PR in the generated release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Publish the design token library to NPM
3 participants