@datagouv/components-next 1.0.2-dev.130 → 1.0.2-dev.131

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.
Files changed (2) hide show
  1. package/README.md +7 -6
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -65,7 +65,7 @@ app.vueApp.use(datagouv, {
65
65
  `@datagouv/components` is using [TailwindCSS](https://tailwindcss.com/docs) and some [DSFR](https://www.systeme-de-design.gouv.fr/) right now. The user needs to provide the correct version of the DSFR. Concerning TailwindCSS, there are two modes:
66
66
 
67
67
  1. If the user is using TailwindCSS, it can import a full TailwindCSS config with `@import "@datagouv/components-next/assets/main.css";`, then build the CSS via TailwindCSS CLI or Vite plugin.
68
- 2. If the user is not using TailwindCSS, it can import an already built CSS file with `@import '@datagouv/components-next/dist/components.css';`. Note @dev, this file should be built before publishing the package to NPM with `npm run css`. For more details on the [technology stack](../README.md#-technology-stack), see the main README.
68
+ 2. If the user is not using TailwindCSS, it can import an already built CSS file with `@import '@datagouv/components-next/dist/components.css';`. Note @dev, this file should be built before publishing the package to PNPM with `pnpm run css`. For more details on the [technology stack](../README.md#-technology-stack), see the main README.
69
69
 
70
70
  ### I18n
71
71
 
@@ -94,8 +94,8 @@ For general development guidelines and contributing, see the [contributing secti
94
94
  This component library uses both ESLint and Prettier for code quality and formatting:
95
95
 
96
96
  ```bash
97
- npm run lint # Lint and auto-fix ESLint issues
98
- npm run format # Format code with Prettier
97
+ pnpm run lint # Lint and auto-fix ESLint issues
98
+ pnpm run format # Format code with Prettier
99
99
  ```
100
100
 
101
101
  **Note:** Make sure to run both commands before submitting contributions to ensure consistent code style.
@@ -172,10 +172,10 @@ To make a new release, you have to :
172
172
 
173
173
  ### Update the version
174
174
 
175
- Use the dedicated npm command, with the correct parameter :
175
+ Use the dedicated pnpm command, with the correct parameter :
176
176
 
177
177
  ```
178
- npm version VERSION
178
+ pnpm version VERSION
179
179
  ```
180
180
 
181
181
  Where VERSION is :
@@ -187,7 +187,8 @@ Additional labels for pre-release and build metadata are available as extensions
187
187
  ### Publish to NPM
188
188
 
189
189
  ```
190
- npm run publish-stable
190
+ pnpm login
191
+ pnpm run publish-stable
191
192
  ```
192
193
 
193
194
  ## 📄 License
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@datagouv/components-next",
3
- "version": "1.0.2-dev.130",
3
+ "version": "1.0.2-dev.131",
4
4
  "private": false,
5
5
  "type": "module",
6
6
  "engines": {