@atlassian/clientside-extensions-docs 5.1.3 → 5.1.4

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.
@@ -4,7 +4,7 @@ platform: server
4
4
  product: clientside-extensions
5
5
  category: devguide
6
6
  subcategory: how-to
7
- date: '2025-09-15'
7
+ date: '2026-01-02'
8
8
  ---
9
9
 
10
10
  # Setting up the CSE webpack plugin
@@ -168,17 +168,3 @@ module.exports = {
168
168
  },
169
169
  };
170
170
  ```
171
-
172
- ## 5. Self troubleshooting tool
173
-
174
- We provide a tool that helps troubleshoot the configuration of webpack and Atlassian P2 projects.
175
-
176
- To check if your project was configured correctly, open a terminal and navigate to the root directory of your project. Next, run the troubleshooting command:
177
-
178
- ```shell
179
- npx @atlassian/wrm-troubleshooting
180
- ```
181
-
182
- The tool will ask you a few questions and guide you if it finds issues with your projects' configuration.
183
-
184
- You can read more about the troubleshooting tool on the [NPM page for the `@atlassian/wrm-troubleshooting` package](https://www.npmjs.com/package/@atlassian/wrm-troubleshooting).
@@ -4,7 +4,7 @@ platform: server
4
4
  product: clientside-extensions
5
5
  category: reference
6
6
  subcategory: webpack
7
- date: '2025-09-15'
7
+ date: '2026-01-02'
8
8
  ---
9
9
 
10
10
  # Annotations
@@ -4,7 +4,7 @@ platform: server
4
4
  product: clientside-extensions
5
5
  category: reference
6
6
  subcategory: webpack
7
- date: '2025-09-15'
7
+ date: '2026-01-02'
8
8
  ---
9
9
 
10
10
  # Webpack plugin
@@ -70,22 +70,3 @@ module.exports = {
70
70
  /*...*/
71
71
  };
72
72
  ```
73
-
74
- ## Self troubleshooting tool
75
-
76
- We provide a tool that helps troubleshoot the configuration of webpack and Atlassian P2 projects.
77
-
78
- To check if your project was configured correctly, open a terminal and navigate to the root directory of your project. Next, run the troubleshooting command:
79
-
80
- ```shell
81
- npx @atlassian/wrm-troubleshooting
82
- ```
83
-
84
- The tool will ask you a few questions and guide you if it finds issues with your projects' configuration.
85
-
86
- You can read more about the troubleshooting tool on the [NPM page for the `@atlassian/wrm-troubleshooting` package][https://www.npmjs.com/package/@atlassian/wrm-troubleshooting].
87
-
88
- ### Enable verbose (debug) output
89
-
90
- It may be hard to understand what files were scanned and what the result of that was, by setting the environment variable `CSE_DEBUG=true`,
91
- some additional information will be printed out while running.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@atlassian/clientside-extensions-docs",
3
- "version": "5.1.3",
3
+ "version": "5.1.4",
4
4
  "description": "Holds the official documentation for Altassian Server client-side extensions API.",
5
5
  "license": "BSD-3-Clause",
6
6
  "homepage": "https://bitbucket.org/atlassian/atlassian-clientside-extensions#readme",
@@ -80,5 +80,5 @@
80
80
  "devDependencies": {
81
81
  "@atlassian/doc-scripts": "^11.1.0"
82
82
  },
83
- "gitHead": "8bca519daf2bc3459ebe9531b3461a1ecd1be7b5"
83
+ "gitHead": "96fae8ce4321a1d0a0a613910b9d5fedced96ea8"
84
84
  }