@atlassian/clientside-extensions-docs - npm Package Compare versions

Comparing version 2.4.3 to 2.4.4

content/server/framework/clientside-extensions/reference/webpack-plugin/webpack-plugin.md

		@@ -7,3 +7,3 @@ ---
		subcategory: webpack
		date: '2021-10-12'
		date: '2022-07-26'
		---
		@@ -29,8 +29,16 @@
		<td>pattern*</td>
		<td>Glob pattern to specify which files should be consider as entry-points.</td>
		<td>Glob pattern to specify which files should be considered as entry-points.</td>
		</tr>
		<tr>
		<td>ignore</td>
		<td>Define patterns of files to ignore when searching for clientside-extension annotations.</td>
		</tr>
		<tr>
		<td>cwd</td>
		<td>Configure a working directory to look for entry-points</td>
		<td>Configure a working directory to look for entry-points.</td>
		</tr>
		<tr>
		<td>xmlDescriptors</td>
		<td>Define the output filename that will contain the XML plugin module descriptors.</td>
		</tr>
		</tbody>
		@@ -81,1 +89,6 @@ </table>
		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].

		### Enable verbose (debug) output

		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`,
		some additional information will be printed out while running.

package.json

		{
		"name": "@atlassian/clientside-extensions-docs",
		"version": "2.4.3",
		"version": "2.4.4",
		"description": "Holds the official documentation for Altassian Server client-side extensions API.",
		@@ -80,5 +80,5 @@ "license": "BSD-3-Clause",
		"optionalDependencies": {
		"@atlassian/doc-scripts": "^5.0.1"
		"@atlassian/doc-scripts": "^7.1.0"
		},
		"gitHead": "9ce0846abde618df3383f87d259023088f04d21b"
		"gitHead": "f231082bf82640c83abf57ed1c83c1b669ea69f3"
		}

Improved metrics