lux-design-system 7.6.3 → 7.7.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -4,13 +4,15 @@
4
4
 
5
5
  ## Adding Lux to an application or website
6
6
 
7
- * [Instructions for adding lux](docs/adding_lux.md)
8
- * If you are looking for examples, take a look at one of the [many PUL applications and sites that use Lux](docs/lux_usage.md).
7
+ - [Instructions for adding lux](docs/adding_lux.md)
8
+ - If you are looking for examples, take a look at one of the [many PUL applications and sites that use Lux](docs/lux_usage.md).
9
9
 
10
10
  ## Project setup
11
+
11
12
  ```
12
13
  npm install
13
14
  ```
15
+
14
16
  ### Serve the styleguide documentation locally
15
17
 
16
18
  ```
@@ -19,28 +21,28 @@ npm run styleguide
19
21
 
20
22
  ### Running tests
21
23
 
22
- * Run all tests with `npm run test`
23
- * Run a single test file with `npx vitest tests/unit/specs/components/luxGridItem.spec.js`
24
- * Run a single test with the name of the test from the `it()` call: `npx vitest -t "should have the appropriate class to define the columns"`
24
+ - Run all tests with `npm run test`
25
+ - Run a single test file with `npx vitest tests/unit/specs/components/luxGridItem.spec.js`
26
+ - Run a single test with the name of the test from the `it()` call: `npx vitest -t "should have the appropriate class to define the columns"`
25
27
 
26
28
  #### Running playwright
27
29
 
28
- Playwright is an end to end testing harness. It is installed as a packge in the system and is run as part if the CI testing suite.
30
+ Playwright is an end to end testing harness. It is installed as a packge in the system and is run as part if the CI testing suite.
29
31
 
30
32
  On first installation you must run `npx playwright install` to get the browsers for playwright.
31
33
 
32
- * to run the tests without a ui and on multiple browsers
33
- ```
34
- npx playwright test
35
- ```
36
- * to run the test with screen shots of each step
34
+ - to run the tests without a ui and on multiple browsers
35
+ ```
36
+ npx playwright test
37
+ ```
38
+ - to run the test with screen shots of each step
37
39
  ```
38
40
  npx playwright test --ui`
39
41
  ```
40
42
 
41
43
  ## Release a new version
42
44
 
43
- This requires you to have an account on npm with 2fa enabled. You will also
45
+ This requires you to have an account on npm with 2fa enabled. You will also
44
46
  need to be part of the PULibrary organization on npm.
45
47
 
46
48
  ```
@@ -52,37 +54,44 @@ npm run release
52
54
  ```
53
55
 
54
56
  ### Tips
55
- * If you have a passphrase on your ssh key, run ssh-add ~/.ssh/id_ed25519 (or wherever your key is located).
56
- * If you use a security key, rather than an authenticator app, for two-factor authentication in npmjs.com, make sure that "Require two-factor authentication for write actions" is not checked in your account 2FA settings.
57
- * Go to:Account -> Manage Two-Factor Authentication -> Uncheck 'Additional Options' -> Update Preferences. If it is checked, np will ask you for an OTP from your phone, and won't allow you to push without it.
57
+
58
+ - If you have a passphrase on your ssh key, run ssh-add ~/.ssh/id_ed25519 (or wherever your key is located).
59
+ - If you use a security key, rather than an authenticator app, for two-factor authentication in npmjs.com, make sure that "Require two-factor authentication for write actions" is not checked in your account 2FA settings.
60
+ - Go to:Account -> Manage Two-Factor Authentication -> Uncheck 'Additional Options' -> Update Preferences. If it is checked, np will ask you for an OTP from your phone, and won't allow you to push without it.
58
61
 
59
62
  ## Deploy the styleguide to GitHub Pages
63
+
60
64
  ```
61
65
  npm run deploy
62
66
  ```
67
+
63
68
  This will update the docs at [https://pulibrary.github.io/lux-design-system/](https://pulibrary.github.io/lux-design-system/).
64
69
  Please note: For informational purposes only. Don't do this outside of a release!
65
70
 
66
71
  ## Linting
72
+
67
73
  We are using the eslint_plugin-prettier to lint our files. To adjust the lint format settings, please use the `.prettierrc` file. Code linting rules should be set in `eslintrc.js`.
68
74
 
69
75
  ### Style Linting
76
+
70
77
  We are using stylelint and stylelint-config-standard-scss to lint scss files. To disable or customize any rules use the `.stylelintrc.json`. Run `npx stylelint "**/*.scss"` to lint the scss files.
71
78
 
72
79
  ## Customize configuration
80
+
73
81
  See [Configuration Reference](https://cli.vuejs.org/config/).
74
82
 
75
83
  ## Using a local copy of lux-design-system in your project
76
84
 
77
85
  1. `yarn global add yalc` (yalc has to be installed globally, it doesn't work as part of the package.json)
78
- 2. In lux-design-system run: `npm run build && yarn exec yalc publish`
79
- You should see a note that it's published in store
80
- 3. In the application where lux-design-system is installed,
81
- run: `yarn exec yalc add lux-design-system`
86
+ 2. In lux-design-system run: `npm run build && yarn exec yalc publish`
87
+ You should see a note that it's published in store
88
+ 3. In the application where lux-design-system is installed,
89
+ run: `yarn exec yalc add lux-design-system`
82
90
  4. Sometimes, your application's vite will have cached the old version.
83
- If you are not seeing your changes, in your application directory run:
84
- * `bundle exec vite clobber` for ruby projects
85
- * `yarn dev --force` for Vue projects
91
+ If you are not seeing your changes, in your application directory run:
92
+
93
+ - `bundle exec vite clobber` for ruby projects
94
+ - `yarn dev --force` for Vue projects
86
95
 
87
96
  ## Upgrade Instructions
88
97