@phun-ky/speccer 11.2.10 → 11.2.12

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
@@ -2,13 +2,25 @@
2
2
 
3
3
  ![Speccer hero, with logo and slogan: A zero dependency package to annotate or highlight elements](./public/speccer-hero.png)
4
4
 
5
- [![Commitizen friendly](https://img.shields.io/badge/commitizen-friendly-brightgreen.svg)](http://commitizen.github.io/cz-cli/) [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-green.svg)](http://makeapullrequest.com) [![SemVer 2.0](https://img.shields.io/badge/SemVer-2.0-green.svg)](http://semver.org/spec/v2.0.0.html) ![npm version](https://img.shields.io/npm/v/@phun-ky/speccer) ![issues](https://img.shields.io/github/issues/phun-ky/speccer) ![license](https://img.shields.io/npm/l/@phun-ky/speccer) ![size](https://img.shields.io/bundlephobia/min/@phun-ky/speccer) ![npm](https://img.shields.io/npm/dm/%40phun-ky/speccer) ![GitHub Repo stars](https://img.shields.io/github/stars/phun-ky/speccer) [![codecov](https://codecov.io/gh/phun-ky/speccer/graph/badge.svg?token=VA91DL7ZLZ)](https://codecov.io/gh/phun-ky/speccer) [![build](https://github.com/phun-ky/speccer/actions/workflows/check.yml/badge.svg)](https://github.com/phun-ky/speccer/actions/workflows/check.yml)
5
+ [![Commitizen friendly](https://img.shields.io/badge/commitizen-friendly-brightgreen.svg)](http://commitizen.github.io/cz-cli/)
6
+ [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-green.svg)](http://makeapullrequest.com)
7
+ [![SemVer 2.0](https://img.shields.io/badge/SemVer-2.0-green.svg)](http://semver.org/spec/v2.0.0.html)
8
+ ![npm version](https://img.shields.io/npm/v/@phun-ky/speccer)
9
+ ![issues](https://img.shields.io/github/issues/phun-ky/speccer)
10
+ ![license](https://img.shields.io/npm/l/@phun-ky/speccer)
11
+ ![size](https://img.shields.io/bundlephobia/min/@phun-ky/speccer)
12
+ ![npm](https://img.shields.io/npm/dm/%40phun-ky/speccer)
13
+ ![GitHub Repo stars](https://img.shields.io/github/stars/phun-ky/speccer)
14
+ [![codecov](https://codecov.io/gh/phun-ky/speccer/graph/badge.svg?token=VA91DL7ZLZ)](https://codecov.io/gh/phun-ky/speccer)
15
+ [![build](https://github.com/phun-ky/speccer/actions/workflows/check.yml/badge.svg)](https://github.com/phun-ky/speccer/actions/workflows/check.yml)
6
16
 
7
17
  ## About
8
18
 
9
19
  ![Image of speccer](./public/speccer-pin-parent-align-light.png)
10
20
 
11
- **SPECCER** was originally created to simplify documenting components in a design system, but it can be used to annotate or highlight any HTML element on a webpage. If you need to draw attention to elements, **SPECCER** is your tool!
21
+ **SPECCER** was originally created to simplify documenting components in a
22
+ design system, but it can be used to annotate or highlight any HTML element on a
23
+ webpage. If you need to draw attention to elements, **SPECCER** is your tool!
12
24
 
13
25
  ## Table of Contents<!-- omit from toc -->
14
26
 
@@ -35,7 +47,7 @@
35
47
  - [Custom literals](#custom-literals)
36
48
  - [Subtle anatomy](#subtle-anatomy)
37
49
  - [Curly brackets](#curly-brackets)
38
- - [Pin programatically](#pin-programatically)
50
+ - [Pin programmatically](#pin-programmatically)
39
51
  - [Element typography](#element-typography)
40
52
  - [Syntax highlighting for typography](#syntax-highlighting-for-typography)
41
53
  - [Grid spacing](#grid-spacing)
@@ -84,7 +96,9 @@ speccer();
84
96
 
85
97
  #### Lazy loading
86
98
 
87
- If you're importing **SPECCER** instead of with a script tag, [you can use the following approach](https://codepen.io/phun-ky/pen/VwRRLyY) to apply lazy loading:
99
+ If you're importing **SPECCER** instead of with a script tag,
100
+ [you can use the following approach](https://codepen.io/phun-ky/pen/VwRRLyY) to
101
+ apply lazy loading:
88
102
 
89
103
  ```javascript
90
104
  import { pin } from "https://esm.sh/@phun-ky/speccer";
@@ -146,7 +160,8 @@ And then follow the steps below to display the specifications you want :)
146
160
 
147
161
  #### Advanced usage
148
162
 
149
- If you want to control **SPECCER** a bit more, you have some options. Apply one of these attributes to the script element for different types of initialization:
163
+ If you want to control **SPECCER** a bit more, you have some options. Apply one
164
+ of these attributes to the script element for different types of initialization:
150
165
 
151
166
  ```html
152
167
  <script src="../speccer.js" data-<manual|instant|dom|lazy></script>
@@ -165,7 +180,8 @@ Or with a CDN:
165
180
  | `data-dom` | Waits for `DOMContentLoaded` |
166
181
  | `data-lazy` | Lazy loads `speccer()` per specced element |
167
182
 
168
- If no attribute is applied, it will default to `data-dom`, as in, it will initialize when `DOMContentLoaded` is fired.
183
+ If no attribute is applied, it will default to `data-dom`, as in, it will
184
+ initialize when `DOMContentLoaded` is fired.
169
185
 
170
186
  ### React
171
187
 
@@ -214,7 +230,8 @@ Use the following attribute to display element padding and margin:
214
230
  <div data-speccer="spacing [padding|margin] [bound]" class="…"></div>
215
231
  ```
216
232
 
217
- This will display the element _and all of it's children_ padding and margin, unless you specify `padding` and `margin`
233
+ This will display the element _and all of it's children_ padding and margin,
234
+ unless you specify `padding` and `margin`
218
235
 
219
236
  ![Image of the spacing feature in dark mode](./public/speccer-spacing-dark.png)
220
237
 
@@ -242,7 +259,8 @@ Display dimensions with:
242
259
  ></div>
243
260
  ```
244
261
 
245
- Where `height` and `width` comes with placement flags. Default for `height` is `left`, default for `width` is `top`.
262
+ Where `height` and `width` comes with placement flags. Default for `height` is
263
+ `left`, default for `width` is `top`.
246
264
 
247
265
  ![Image of the measure feature](./public/speccer-measure-spacing-example-dark.png)
248
266
 
@@ -260,7 +278,8 @@ This will give a slimmer look and feel.
260
278
 
261
279
  ##### Subtle slim measure
262
280
 
263
- Use a subtle style for the slim option, uses a dashed line instead of a solid line:
281
+ Use a subtle style for the slim option, uses a dashed line instead of a solid
282
+ line:
264
283
 
265
284
  ```html
266
285
  <div data-speccer="measure slim height left subtle" class="…"></div>
@@ -272,7 +291,8 @@ This will give a dashed border.
272
291
 
273
292
  ![Image of speccer](./public/anatomy.png)
274
293
 
275
- In your component examples, use the following attribute. Remember to use the `data-speccer="pin-area"`-attribute on a parent element to scope the marking.
294
+ In your component examples, use the following attribute. Remember to use the
295
+ `data-speccer="pin-area"`-attribute on a parent element to scope the marking.
276
296
 
277
297
  ```html
278
298
  <div data-speccer="pin-area">
@@ -327,10 +347,11 @@ You can also align the pins to the parent container.
327
347
  </div>
328
348
  ```
329
349
 
330
- > [!NOTE]
331
- > Only works with `pin [left|right|top|bottom]`, and not with `enclose`, `bracket` or `curly`!
350
+ > [!NOTE] Only works with `pin [left|right|top|bottom]`, and not with `enclose`,
351
+ > `bracket` or `curly`!
332
352
 
333
- The lines from the element to the pin is drawn with a svg path and circle, so remember to add the following svg into your document:
353
+ The lines from the element to the pin is drawn with a svg path and circle, so
354
+ remember to add the following svg into your document:
334
355
 
335
356
  ```html
336
357
  <svg
@@ -355,7 +376,8 @@ The lines from the element to the pin is drawn with a svg path and circle, so re
355
376
 
356
377
  ![Image of text pin option](./public/speccer-pin-text-light.png)
357
378
 
358
- If you want _text-in-place_ pinning feature, instead of referencing the pins, you can use the `text` feature:
379
+ If you want _text-in-place_ pinning feature, instead of referencing the pins,
380
+ you can use the `text` feature:
359
381
 
360
382
  ```html
361
383
  <input
@@ -372,7 +394,8 @@ If you want _text-in-place_ pinning feature, instead of referencing the pins, yo
372
394
 
373
395
  ![Image of japanese literals instead of latin characters](./public/speccer-pin-symbols-light.png)
374
396
 
375
- You can use custom literals by assigned a global variable with the literals you want:
397
+ You can use custom literals by assigned a global variable with the literals you
398
+ want:
376
399
 
377
400
  ```js
378
401
  window.SPECCER_LITERALS = [
@@ -396,8 +419,7 @@ Or with a data attribute on the `data-speccer="pin-area"`-element:
396
419
  </div>
397
420
  ```
398
421
 
399
- > [!TIP]
400
- > Try it out with emoticons!
422
+ > [!TIP] Try it out with emoticons!
401
423
  >
402
424
  > ```js
403
425
  > window.SPECCER_LITERALS = [
@@ -422,14 +444,15 @@ This will give a dashed border, and a more subtle pin style.
422
444
 
423
445
  #### Curly brackets
424
446
 
425
- You can use curly brackets with the `curly` tag in `data-speccer` along side `pin bracket` to provide a more sleek style.
447
+ You can use curly brackets with the `curly` tag in `data-speccer` along side
448
+ `pin bracket` to provide a more sleek style.
426
449
 
427
450
  ![Image of curly option for anatomy](./public/speccer-pin-curly-light.png)
428
451
 
429
- > [!NOTE]
430
- > Only works with `pin bracket`
452
+ > [!NOTE] Only works with `pin bracket`
431
453
 
432
- The curly brackets are made with SVG paths, and it is required to have the following snippet on your page for it to render:
454
+ The curly brackets are made with SVG paths, and it is required to have the
455
+ following snippet on your page for it to render:
433
456
 
434
457
  ```html
435
458
  <svg
@@ -448,9 +471,11 @@ The curly brackets are made with SVG paths, and it is required to have the follo
448
471
  </svg>
449
472
  ```
450
473
 
451
- #### Pin programatically
474
+ #### Pin programmatically
452
475
 
453
- from v9.5 you can utilize the `pin` feature to annotate or highlight the anatomy of an element programaticaly. [Here is an example with a click event](https://codepen.io/phun-ky/pen/LYKOWyP).
476
+ from v9.5 you can utilize the `pin` feature to annotate or highlight the anatomy
477
+ of an element programmatically.
478
+ [Here is an example with a click event](https://codepen.io/phun-ky/pen/LYKOWyP).
454
479
 
455
480
  [Kazam_screencast_00002.webm](https://github.com/user-attachments/assets/5c78cece-de46-4876-81f2-98c9108a2103)
456
481
 
@@ -466,12 +491,15 @@ Display typography details:
466
491
 
467
492
  This will place a box to display typography information. Default is `left`.
468
493
 
469
- > [!NOTE]
470
- > `getComputedStyles` are used to get the _computed_ values, so for example, a `line-height` set to `1.5` will be presented in pixels, like `96px` if the `font-size` is set to `64px`.
494
+ > [!NOTE] > `getComputedStyles` are used to get the _computed_ values, so for
495
+ > example, a `line-height` set to `1.5` will be presented in pixels, like `96px`
496
+ > if the `font-size` is set to `64px`.
471
497
 
472
498
  #### Syntax highlighting for typography
473
499
 
474
- If you want to produce a box that uses `pre` and `code` tags with support for syntax highlighting ([PrismJS](https://prismjs.com/) compatible), add `syntax` to the `data-speccer="typography"` attribute.
500
+ If you want to produce a box that uses `pre` and `code` tags with support for
501
+ syntax highlighting ([PrismJS](https://prismjs.com/) compatible), add `syntax`
502
+ to the `data-speccer="typography"` attribute.
475
503
 
476
504
  ```html
477
505
  <p data-speccer="typography syntax right" class="…">Some text</p>
@@ -513,7 +541,7 @@ Here is an example with these colors and overrides:
513
541
  }
514
542
  ```
515
543
 
516
- ![Screenshot of typgraphy with different syntax theme](./public/speccer-typography-syntax-light.png)
544
+ ![Screenshot of typography with different syntax theme](./public/speccer-typography-syntax-light.png)
517
545
 
518
546
  ### Grid spacing
519
547
 
@@ -527,8 +555,8 @@ In your component examples, use the following attribute on your grid container.
527
555
  <div data-speccer="grid" …>…</div>
528
556
  ```
529
557
 
530
- > [!TIP]
531
- > If you only want to display `rows` or `columns`, use this syntax (default is both with `grid` only):
558
+ > [!TIP] If you only want to display `rows` or `columns`, use this syntax
559
+ > (default is both with `grid` only):
532
560
  >
533
561
  > ```html
534
562
  > <div data-speccer="grid [rows|columns]" …>…</div>
@@ -550,39 +578,50 @@ In your component examples, use the following attribute.
550
578
 
551
579
  ### A11y notation
552
580
 
553
- With **SPECCER**, you can also display accessibility notation, like [Accessibility Bluelines](https://dribbble.com/shots/6269661-Accessibility-Bluelines?utm_source=Clipboard_Shot&utm_campaign=jeremyelder&utm_content=Accessibility%20Bluelines&utm_medium=Social_Share&utm_source=Clipboard_Shot&utm_campaign=jeremyelder&utm_content=Accessibility%20Bluelines&utm_medium=Social_Share) or [A11y Annotation Kit](https://www.figma.com/community/file/953682768192596304):
581
+ With **SPECCER**, you can also display accessibility notation, like
582
+ [Accessibility Bluelines](https://dribbble.com/shots/6269661-Accessibility-Bluelines?utm_source=Clipboard_Shot&utm_campaign=jeremyelder&utm_content=Accessibility%20Bluelines&utm_medium=Social_Share&utm_source=Clipboard_Shot&utm_campaign=jeremyelder&utm_content=Accessibility%20Bluelines&utm_medium=Social_Share)
583
+ or
584
+ [A11y Annotation Kit](https://www.figma.com/community/file/953682768192596304):
554
585
 
555
- Prior art: [Jeremy Elder](https://twitter.com/JeremyElder) and [Stephanie Hagadorn](https://shagadorn.work/)
586
+ Prior art: [Jeremy Elder](https://twitter.com/JeremyElder) and
587
+ [Stephanie Hagadorn](https://shagadorn.work/)
556
588
 
557
589
  #### Tab stops
558
590
 
559
591
  ![Screenshot of speccer a11y tab stops in use](./public/speccer-a11y-tabstops-light.png)
560
592
 
561
- If you want to display tab stops, append `data-speccer="a11y tabstops"` as an attribute to the container you want to display the tab stops in.
593
+ If you want to display tab stops, append `data-speccer="a11y tabstops"` as an
594
+ attribute to the container you want to display the tab stops in.
562
595
 
563
596
  #### Landmarks and regions
564
597
 
565
598
  ![Screenshot of speccer a11y landmarks in use](./public/speccer-a11y-landmarks-light.png)
566
599
 
567
- If you want to display landmarks and regions, append `data-speccer="a11y landmark"` as an attribute to the container you want to display the landmarks and regions in.
600
+ If you want to display landmarks and regions, append
601
+ `data-speccer="a11y landmark"` as an attribute to the container you want to
602
+ display the landmarks and regions in.
568
603
 
569
604
  #### Headings
570
605
 
571
606
  ![Screenshot of speccer a11y headings in use](./public/speccer-a11y-headings-light.png)
572
607
 
573
- If you want to display headings, append `data-speccer="a11y headings"` as an attribute to the container you want to display the headings in.
608
+ If you want to display headings, append `data-speccer="a11y headings"` as an
609
+ attribute to the container you want to display the headings in.
574
610
 
575
611
  #### Autocomplete
576
612
 
577
613
  ![Screenshot of speccer a11y autocomplete in use](./public/speccer-a11y-autocomplete-light.png)
578
614
 
579
- If you want to display autocomplete, append `data-speccer="a11y autocomplete"` as an attribute to the container you want to display the autocomplete in.
615
+ If you want to display autocomplete, append `data-speccer="a11y autocomplete"`
616
+ as an attribute to the container you want to display the autocomplete in.
580
617
 
581
618
  #### Keys and shortcut
582
619
 
583
620
  ![Screenshot of speccer a11y shortcuts in use](./public/speccer-a11y-shortcuts-light.png)
584
621
 
585
- If you want to display the shortcut with keys used for elements, use `data-speccer="a11y shortcut"` and `data-speccer-a11y-shortcut="<shortcut>"` on the element that uses this shortcut:
622
+ If you want to display the shortcut with keys used for elements, use
623
+ `data-speccer="a11y shortcut"` and `data-speccer-a11y-shortcut="<shortcut>"` on
624
+ the element that uses this shortcut:
586
625
 
587
626
  ```html
588
627
  <button
@@ -598,7 +637,9 @@ If you want to display the shortcut with keys used for elements, use `data-specc
598
637
 
599
638
  ![Screenshot of speccer in a dark mode example](./public/speccer-measure-spacing-example-dark.png)
600
639
 
601
- Allthough the styling works nicely with dark mode, you can use the provided CSS variables to customize the look and feel. If more control is needed, you can use CSS overrides :)
640
+ Although the styling works nicely with dark mode, you can use the provided CSS
641
+ variables to customize the look and feel. If more control is needed, you can use
642
+ CSS overrides :)
602
643
 
603
644
  ```css
604
645
  .ph-speccer.speccer {
@@ -652,9 +693,9 @@ Allthough the styling works nicely with dark mode, you can use the provided CSS
652
693
  --ph-speccer-line-width-negative: -1.5px;
653
694
  --ph-speccer-opacity-20: 0.2;
654
695
  --ph-speccer-opacity-40: 0.4;
655
- --ph-speccer-font-family: 'Menlo for Powerline', 'Menlo Regular for Powerline',
656
- 'DejaVu Sans Mono', Consolas, Monaco, 'Andale Mono', 'Ubuntu Mono',
657
- monospace;
696
+ --ph-speccer-font-family:
697
+ 'Menlo for Powerline', 'Menlo Regular for Powerline', 'DejaVu Sans Mono',
698
+ Consolas, Monaco, 'Andale Mono', 'Ubuntu Mono', monospace;
658
699
  --ph-speccer-font-size: 12px;
659
700
  --ph-speccer-transition-default: all 2s cubic-bezier(0.4, 0, 0.2, 1);
660
701
  }
@@ -662,7 +703,8 @@ Allthough the styling works nicely with dark mode, you can use the provided CSS
662
703
 
663
704
  ## API
664
705
 
665
- Full API documentation is available [here](https://github.com/phun-ky/speccer/blob/main/api/README.md).
706
+ Full API documentation is available
707
+ [here](https://github.com/phun-ky/speccer/blob/main/api/README.md).
666
708
 
667
709
  ## Development
668
710
 
@@ -681,28 +723,48 @@ $ npm test
681
723
 
682
724
  ## Contributing
683
725
 
684
- Want to contribute? Please read the [CONTRIBUTING.md](https://github.com/phun-ky/speccer/blob/main/CONTRIBUTING.md) and [CODE_OF_CONDUCT.md](https://github.com/phun-ky/speccer/blob/main/CODE_OF_CONDUCT.md)
726
+ Want to contribute? Please read the
727
+ [CONTRIBUTING.md](https://github.com/phun-ky/speccer/blob/main/CONTRIBUTING.md)
728
+ and
729
+ [CODE_OF_CONDUCT.md](https://github.com/phun-ky/speccer/blob/main/CODE_OF_CONDUCT.md)
685
730
 
686
731
  ## License
687
732
 
688
- This project is licensed under the MIT License - see the [LICENSE](https://github.com/phun-ky/speccer/blob/main/LICENSE) file for details.
733
+ This project is licensed under the MIT License - see the
734
+ [LICENSE](https://github.com/phun-ky/speccer/blob/main/LICENSE) file for
735
+ details.
689
736
 
690
737
  ## Changelog
691
738
 
692
- See the [CHANGELOG.md](https://github.com/phun-ky/speccer/blob/main/CHANGELOG.md) for details on the latest updates.
739
+ See the
740
+ [CHANGELOG.md](https://github.com/phun-ky/speccer/blob/main/CHANGELOG.md) for
741
+ details on the latest updates.
693
742
 
694
743
  ## FAQ
695
744
 
696
- See the [discussions](https://github.com/phun-ky/speccer/discussions/categories/q-a) for an FAQ or to ask questions if no answer is given.
745
+ See the
746
+ [discussions](https://github.com/phun-ky/speccer/discussions/categories/q-a) for
747
+ an FAQ or to ask questions if no answer is given.
697
748
 
698
749
  ## Sponsor me
699
750
 
700
- I'm an Open Source evangelist, creating stuff that does not exist yet to help get rid of secondary activities and to enhance systems already in place, be it documentation or web sites.
751
+ I'm an Open Source evangelist, creating stuff that does not exist yet to help
752
+ get rid of secondary activities and to enhance systems already in place, be it
753
+ documentation or web sites.
701
754
 
702
- The sponsorship is an unique opportunity to alleviate more hours for me to maintain my projects, create new ones and contribute to the large community we're all part of :)
755
+ The sponsorship is an unique opportunity to alleviate more hours for me to
756
+ maintain my projects, create new ones and contribute to the large community
757
+ we're all part of :)
703
758
 
704
759
  [Support me on GitHub Sponsors](https://github.com/sponsors/phun-ky).
705
760
 
706
761
  ![Speccer banner, with logo and slogan: A zero dependency package to annotate or highlight elements](./public/speccer-banner.png)
707
762
 
708
- p.s. **Ukraine is still under brutal Russian invasion. A lot of Ukrainian people are hurt, without shelter and need help**. You can help in various ways, for instance, directly helping refugees, spreading awareness, putting pressure on your local government or companies. You can also support Ukraine by donating e.g. to [Red Cross](https://www.icrc.org/en/donate/ukraine), [Ukraine humanitarian organisation](https://savelife.in.ua/en/donate-en/#donate-army-card-weekly) or [donate Ambulances for Ukraine](https://www.gofundme.com/f/help-to-save-the-lives-of-civilians-in-a-war-zone).
763
+ p.s. **Ukraine is still under brutal Russian invasion. A lot of Ukrainian people
764
+ are hurt, without shelter and need help**. You can help in various ways, for
765
+ instance, directly helping refugees, spreading awareness, putting pressure on
766
+ your local government or companies. You can also support Ukraine by donating
767
+ e.g. to [Red Cross](https://www.icrc.org/en/donate/ukraine),
768
+ [Ukraine humanitarian organisation](https://savelife.in.ua/en/donate-en/#donate-army-card-weekly)
769
+ or
770
+ [donate Ambulances for Ukraine](https://www.gofundme.com/f/help-to-save-the-lives-of-civilians-in-a-war-zone).
@@ -2,7 +2,7 @@
2
2
  * @phun-ky/speccer
3
3
  * A script to annotate, show spacing specs and to display typography information in documentation/website on HTML elements
4
4
  * @author Alexander Vassbotn Røyne-Helgesen <alexander@phun-ky.net>
5
- * @version 11.2.10
5
+ * @version 11.2.12
6
6
  * @license
7
7
  * Copyright (c) 2018-2025 Alexander Vassbotn Røyne-Helgesen
8
8
  *
package/dist/speccer.js CHANGED
@@ -2,7 +2,7 @@
2
2
  * @phun-ky/speccer
3
3
  * A script to annotate, show spacing specs and to display typography information in documentation/website on HTML elements
4
4
  * @author Alexander Vassbotn Røyne-Helgesen <alexander@phun-ky.net>
5
- * @version 11.2.10
5
+ * @version 11.2.12
6
6
  * @license
7
7
  * Copyright (c) 2018-2025 Alexander Vassbotn Røyne-Helgesen
8
8
  *
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@phun-ky/speccer",
3
- "version": "11.2.10",
3
+ "version": "11.2.12",
4
4
  "description": "A script to annotate, show spacing specs and to display typography information in documentation/website on HTML elements",
5
5
  "keywords": [
6
6
  "a11y",
@@ -83,6 +83,7 @@
83
83
  },
84
84
  "devDependencies": {
85
85
  "@eslint/js": "^9.20.0",
86
+ "@eslint/markdown": "^6.2.2",
86
87
  "@playwright/test": "^1.50.1",
87
88
  "@release-it/conventional-changelog": "^10.0.0",
88
89
  "@rollup/plugin-node-resolve": "^16.0.0",
@@ -106,7 +107,7 @@
106
107
  "jsdom": "^26.0.0",
107
108
  "postcss": "^8.5.2",
108
109
  "postcss-cli": "^11.0.0",
109
- "prettier": "3.5.1",
110
+ "prettier": "3.5.3",
110
111
  "putout": "^38.2.0",
111
112
  "quibble": "^0.9.1",
112
113
  "release-it": "^18.1.2",