Bump the npm group with 5 updates (#711)

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Remi Gau <[email protected]>
Co-authored-by: Christopher J. Markiewicz <[email protected]>

Author: 3 people

.remarkrc

@@ -4,7 +4,7 @@
     "preset-lint-recommended",
     "remark-gfm",
     ["lint-no-duplicate-headings", false],
-    ["lint-list-item-indent", "tab-size"],
+    ["lint-list-item-indent", "tab"],
     ["lint-emphasis-marker", "consistent"],
     ["lint-maximum-line-length", 500],
     ["lint-maximum-heading-length", false],

docs/blog/posts/2023-03-23-steering-group-minutes.md

@@ -116,22 +116,23 @@ Proposed Solution:
 
 Concern:
 
--   this appears to be very dwi specific, should the suffixes be dwi
-  specific?
--   Why is datatype not under model label in the [pull request](https://github.com/bids-standard/bids-specification/pull/1280)
-  example?
+-   this appears to be very dwi specific, should the suffixes be dwi specific?
+
+-   Why is datatype not under model label in the [pull request](https://github.com/bids-standard/bids-specification/pull/1280) example?
+
 -   Is the proposed organization of data aligned with user community? -
-  should we request input from community to determine where these
-  results should be stored
--   [https://github.com/bids-standard/bids-specification/issues/751\#issuecomment-820800800](https://github.com/bids-standard/bids-specification/issues/751#issuecomment-820800800)
--   How does this apply to more general data modalities? Like mEEG,
-  SPECT - more use cases beyond dMRI would be helpful
+    should we request input from community to determine where these
+    results should be stored
+    [https://github.com/bids-standard/bids-specification/issues/751\#issuecomment-820800800](https://github.com/bids-standard/bids-specification/issues/751#issuecomment-820800800)
+
+-   How does this apply to more general data modalities? Like mEEG, SPECT - more use cases beyond dMRI would be helpful
+
 -   "BIDS-like derivatives in other modalities:
-  [https://data.donders.ru.nl/collections/di/dccn/DSC_3031000.00_191?0](https://data.donders.ru.nl/collections/di/dccn/DSC_3031000.00_191?0), see also
-  [https://github.com/Donders-Institute/infant-cluster-effectsize](https://github.com/Donders-Institute/infant-cluster-effectsize)
-  (for the scripts that generate the result)
--   Other ideas: tarballs instead of directories, HDF5 files instead of
-  directories.
+    [https://data.donders.ru.nl/collections/di/dccn/DSC_3031000.00_191?0](https://data.donders.ru.nl/collections/di/dccn/DSC_3031000.00_191?0), see also
+    [https://github.com/Donders-Institute/infant-cluster-effectsize](https://github.com/Donders-Institute/infant-cluster-effectsize)
+    (for the scripts that generate the result)
+
+-   Other ideas: tarballs instead of directories, HDF5 files instead of directories.
 
 BIDS Derivatives Retreat
 
@@ -141,18 +142,19 @@ BIDS Derivatives Retreat
 Summary of the PET-BIDS derivatives meeting
 
 -   Meeting happened 2 weeks ago (March 10th)
--   Mostly an onboarding meeting for the importance and relevance of
-  PET-BIDS derivatives
--   Raw PET data is now part of BIDS, now the second half of the white
-  paper will address the derivatives aspect of PET
--   The PET users are more clinically oriented, more diverse user
-  groups, less agreement within the community in data standards
--   The community is between two ideas: a more restrictive approach with
-  data types allowed, or free datatypes with detailed provenance
+
+-   Mostly an onboarding meeting for the importance and relevance of PET-BIDS derivatives
+
+-   Raw PET data is now part of BIDS, now the second half of the white paper will address
+    the derivatives aspect of PET
+
+-   The PET users are more clinically oriented, more diverse user groups,
+    less agreement within the community in data standards
+
+-   The community is between two ideas: a more restrictive approach
+    with data types allowed, or free datatypes with detailed provenance
 
 Meeting with the DICOM team
 
--   We need to formalize our current state of affairs, see which terms
-  align/ dont align
--   We need to follow up on email from Kim on Feb 14 asking to present
-  at a dicom committee meeting.
+-   We need to formalize our current state of affairs, see which terms align/ dont align
+-   We need to follow up on email from Kim on Feb 14 asking to present at a dicom committee meeting.

docs/blog/posts/2023-04-13-steering-group-minutes.md

@@ -145,8 +145,7 @@ author: anonymous
 Github pull request - [bids-specification 1441](https://github.com/bids-standard/bids-specification/pull/1441)
 and [bids-specification 1457](https://github.com/bids-standard/bids-specification/pull/1457)
 
--   The requesters want to change from number to integer, it was likely
-  in a previous version but not in the current.
+-   The requesters want to change from number to integer, it was likely in a previous version but not in the current.
 -   The sample is not defined, this could be defined in the json -
 -   This should be fine then
 
@@ -156,63 +155,56 @@ modalities that use channels.tsv files. [bids-specification 436](https://github.
 Github pull request: ENH: Array data in .tsv cells - [bids-specification 1446](https://github.com/bids-standard/bids-specification/issues/1446)
 
 -   We might need an example of nesting
--   80/20 rules may need to apply here where we define rules for
-  examples that occur 80% of the time.
+
+-   80/20 rules may need to apply here where we define rules for examples that occur 80% of the time.
+
 -   Why not just repeat the rows for each channel? Example: the onset
-  time for multiple channels could be listed across multiple rows
-  instead of condescending them into a single row/entry (Ariel will
-  suggest this in the pull request)
+    time for multiple channels could be listed across multiple rows
+    instead of condescending them into a single row/entry (Ariel will
+    suggest this in the pull request)
 
 Github pull request: [DISCUSSION] acknowledge contributors in DOIed
 specs on Zenodo - [bids-specification 66](https://github.com/bids-standard/bids-specification/issues/66)
 
 -   What rule should be used for author order on zenodo DOI?
+
 -   Proposal: use a random number generator for each new push of authors
-  to keep order 'fair' for all, possibly include an alphabetical
-  list on the BIDS website for ease of author identification
+    to keep order 'fair' for all, possibly include an alphabetical
+    list on the BIDS website for ease of author identification
+
 -   **Final decision: alphabetical is simple and standard, order does
-  not imply importance, PR is fine.**
+    not imply importance, PR is fine.**
+
 -   Clarify it explicitly in the text
 
 Journals including badges to indicate BIDS compliant dataset:
 
 -   Aperture is agreeable, their website is under development
--   Suggestions: next journal to approach could be **scientific data**
-  given their familiarity with BIDS.
--   Action: email the Scientific Data editor in chief from the BIDS
-  Steering Committee
+-   Suggestions: next journal to approach could be **scientific data** given their familiarity with BIDS.
+-   Action: email the Scientific Data editor in chief from the BIDS Steering Committee
 -   Question standardization of implementation across journals?
 -   Guio will provide and example draft
 -   Question: who/what will identify BIDS compliant datasets?
--   BIDS validator can, however users can include many \#BIDS IGNORE
-  files
--   Either the validator will need to output bidsignore info or
-  reviewers/editors will need to check the bidsignore files
-  themselves.
+-   BIDS validator can, however users can include many BIDS IGNORE files
+-   Either the validator will need to output bidsignore info or reviewers/editors will need to check the bidsignore files themselves.
 
 OHBM best practice committee
 
--   Cyril: John Pyles has circulated the OHBM doc of BIDS 2- reviewing
-  of the proposal?
+-   Cyril: John Pyles has circulated the OHBM doc of BIDS 2- reviewing of the proposal?
 -   This will be reviewed by individuals external from BIDS
--   There will be multiple versions , not all versions need to be
-  reviewed
--   'What is BIDS' should be presented to the community, who should lead
-  this presentation?
+-   There will be multiple versions , not all versions need to be reviewed
+-   'What is BIDS' should be presented to the community, who should lead this presentation?
 -   Experts from each field?
 
 Was there a podcast ([OHBM Neurosalience](https://www.youtube.com/playlist?list=PLg2e4R8SdhpdIMG7Tb9WAEZA6HRnx8Vsb))
 where Peter Bandettini suggested someone talk about BIDS?
 
--   Originated in October 2022, sounds like a good opportunity for more
-  exposure, Cyril will reply to the email thread
+-   Originated in October 2022, sounds like a good opportunity for more exposure, Cyril will reply to the email thread
 
 Next Meeting Guest:
 
--   possibly JB Poline regarding a new tool (could be posted as an issue
-  on github?)
--   Maintainers met with the functional ultrasound group but they are
-  likely too premature for this meeting.
+-   possibly JB Poline regarding a new tool (could be posted as an issue on github?)
+-   Maintainers met with the functional ultrasound group but they are likely too premature for this meeting.
 
 Cyril: the BIDS retreat is looking for additional funding to increase
 the support for the meeting. Who should be additionally invited?

docs/blog/posts/2023-05-25-steering-group-minutes.md

@@ -68,8 +68,7 @@ Halchenko, Stefan Appelhoff, Kimberly Ray
 
 ## NOTES
 
-**Guest Guy Jones: discuss adding badges to the BIDS compliant datasets
-on Scientific Data Journal website.**
+### Guest Guy Jones: discuss adding badges to the BIDS compliant datasets on Scientific Data Journal website
 
 Guy's Feedback:
 

docs/blog/posts/2024-09-19-steering-group-minutes.md

@@ -52,9 +52,9 @@ There was a clear value in staffing specific roles that was not allocated otherw
 ### Q&A
 
 > Ariel: to move ahead with discussions we started about BIDS governance structure
-(that is around foundation, non-profit, 501(c)3...), I've asked Chris Holdgraf to come and chat with us at an upcoming meeting.
-Chris directs [2i2c](https://2i2c.org/), and has a unique perspective on these issues.
-He's also a BIDS contributor, having worked extensively on the iEEG BEP and related.
+> (that is around foundation, non-profit, 501(c)3...), I've asked Chris Holdgraf to come and chat with us at an upcoming meeting.
+> Chris directs [2i2c](https://2i2c.org/), and has a unique perspective on these issues.
+> He's also a BIDS contributor, having worked extensively on the iEEG BEP and related.
 
 -   **Q:** What was the funding model that worked best for 2i2c?
 

docs/collaboration/reports/google_summer/2024-gsod.md

@@ -20,8 +20,8 @@ Case Study Authors:
 ## Summary
 
 | **# Tech Writers** | **TW Project Hours** | **Budget** | **% Project Completed** |
-|:------------------:|:--------------------:|:----------:|:-----------------------:|
-|          1         |          150         | $6,500 USD |           100%          |
+| ------------------ | -------------------- | ---------- | ----------------------- |
+| 1                  | 150                  | $6,500 USD | 100%                    |
 
 This project was trying to improve the BIDS Online Presence, which consists primarily of its informational websites and the BIDS specification.
 We were able to migrate away from a multitude of websites and condense down to mainly the one “New” BIDS Website.
@@ -52,14 +52,14 @@ The brief proposal format was effectively developed through several consultative
 
 ### Budget
 
-|                                                                                                              |                                                                                              |
-| -------------------------------------------------------------------------------------------------------------| -------------------------------------------------------------------------------------------- |
-| How much money did you ask for?                                                                              | 6500$ USD                                                                                    |
-| How did you come up with this estimate?                                                                      | Writer stipend: 5000$ <br> Mentor stipend: 500$ * 3 mentors <br> (following GSOC practice)   |
-| How many hours of work did you budget for the project?                                                       | Writer: 4 h / wk <br> Mentors: 1 h / wk * 4 mentors = 4 h / wk                               |
-| How many hours of work were actually needed for the project?                                                 | Writer: 5 h / wk <br> Mentors: 1.5 h / week * 4 mentors = 6 h / wk                           |
-| What other expenses did you include in your budget?                                                          | None                                                                                         |
-| Did you run into any budget surprises during the project (for example mis-estimates)? If so, please explain. | Mentor time underestimated. Would allocate  more for additional mentors or more mentor time. |
+|                                                                                                               |                                                                                              |
+| ------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
+| How much money did you ask for?                                                                               | 6500$ USD                                                                                    |
+| How did you come up with this zestimate?                                                                      | Writer stipend: 5000$ <br> Mentor stipend: 500$ * 3 mentors <br> (following GSOC practice)   |
+| How many hours of work did you budget for the project?                                                        | Writer: 4 h / wk <br> Mentors: 1 h / wk * 4 mentors = 4 h / wk                               |
+| How many hours of work were actually needed for the project?                                                  | Writer: 5 h / wk <br> Mentors: 1.5 h / week * 4 mentors = 6 h / wk                           |
+| What other expenses did you include in your budget?                                                           | None                                                                                         |
+| Did you run into any budget surprises during the project (for example mis-estimates)? If so, please explain.  | Mentor time underestimated. Would allocate  more for additional mentors or more mentor time. |
 
 ### Technical Writer Recruitment
 
@@ -92,7 +92,7 @@ And finally, October and November brought the BIDS Impact page together to wrap
 
 #### Planned Deliverables
 
-| Deliverable                                                             | % Complete | Relevant Links                                                                                     |	Notes                                                                                                                                                   |
+| Deliverable                                                             | % Complete | Relevant Links                                                                                     | Notes                                                                                                                                                   |
 | ----------------------------------------------------------------------- | ---------- | -------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Consolidate into one website                                            | 100%       | [new BIDS website](https://bids-website.readthedocs.io/)                                           | Dev site - Planning launch in Q1 2025 to replace the old BIDS website at <https://bids.neuroimaging.io/>                                                |
 | Implement a more friendly main website structure and improve navigation | 100%       | [mkdocs TOC configuration](https://github.com/bids-standard/bids-website/blob/main/mkdocs.yml#L88) | User feedback indicates this created significant improvement ( See: [Metrics](#metrics))                                                                |