@atlassian/clientside-extensions-docs 5.0.0 → 5.1.0-9864e593-me132vr9

package/content/server/framework/clientside-extensions/guides/how-to/setup-webpack-plugin.md

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: devguide
 subcategory: how-to
-date: '2024-09-24'
+date: '2025-06-08'
 ---
 
 # Setting up the CSE webpack plugin
@@ -23,10 +23,10 @@ Add `@atlassian/clientside-extension-webpack-plugin` as a dependency of your pro
 npm install --save-dev @atlassian/clientside-extensions-webpack-plugin
 ```
 
-And make sure to also install its peer dependency: `atlassian-webresource-webpack-plugin`
+And make sure to also install its peer dependency: `@atlassian/webresource-webpack-plugin`
 
 ```
-npm install --save-dev atlassian-webresource-webpack-plugin
+npm install --save-dev @atlassian/webresource-webpack-plugin
 ```
 
 ## 2. Configuring CSE
@@ -64,15 +64,15 @@ module.exports = {
 
 ## 3. Configuring WRM webpack plugin
 
-CSE webpack plugin makes use of [WRM webpack plugin](https://www.npmjs.com/package/atlassian-webresource-webpack-plugin) to generate the
+CSE webpack plugin makes use of [WRM webpack plugin](https://www.npmjs.com/package/@atlassian/webresource-webpack-plugin) to generate the
 resource definitions for your extensions, so you also need to configure it.
 
-In your webpack configuration, import `atlassian-webresource-webpack-plugin` and use as follows:
+In your webpack configuration, import `@atlassian/webresource-webpack-plugin` and use as follows:
 
 ```js
 // #webpack.config.js
 const path = require('path');
-const WrmPlugin = require('atlassian-webresource-webpack-plugin');
+const WrmPlugin = require('@atlassian/webresource-webpack-plugin');
 const CSEPlugin = require('@atlassian/clientside-extensions-webpack-plugin');
 
 const csePlugin = new CSEPlugin({...});
@@ -96,7 +96,7 @@ const providedDependencies = {
  * Configure WRM webpack plugin
  *
  * More info about WRM Webpack Plugin:
- * https://bitbucket.org/atlassianlabs/atlassian-webresource-webpack-plugin
+ * https://bitbucket.org/atlassianlabs/fe-server/src/master/packages/webresource-webpack-plugin
  */
 const wrmPlugin = new WrmPlugin({
     // Your Atlassian Plugin key
@@ -132,7 +132,7 @@ At the end, your webpack configuration should look very similar to the following
 // #webpack.config.js
 const path = require('path');
 const CSEPlugin = require('@atlassian/clientside-extensions-webpack-plugin');
-const WrmPlugin = require('atlassian-webresource-webpack-plugin');
+const WrmPlugin = require('@atlassian/webresource-webpack-plugin');
 
 const targetDirectory = path.join(__dirname, 'target');
 

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

@@ -4,7 +4,7 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: webpack
-date: '2024-09-24'
+date: '2025-06-08'
 ---
 
 # Annotations
@@ -265,7 +265,7 @@ export default PageExtension.factory((container) => {
 The `@condition` annotation allows you to define one or multiple conditions that must be satisfied for the extension to be displayed.
 These conditions are evaluated on the server and are implemented in Java. They are used for determining if the extension should be downloaded and rendered by the client. For compatibility reasons, the condition class needs to implement both `com.atlassian.plugin.web.Condition` and `com.atlassian.webresource.spi.condition.UrlReadingCondition` interfaces, and both implementations should yield the same result.
 
-For more information about the condition's usage please refer to the [examples of Web items documentation](https://developer.atlassian.com/server/framework/atlassian-sdk/web-section-plugin-module/#condition-and-conditions-elements) and check the [documentation of `conditionMap` option from `atlassian-webresource-webpack-plugin`](https://www.npmjs.com/package/atlassian-webresource-webpack-plugin#conditionmap-optional).
+For more information about the condition's usage please refer to the [examples of Web items documentation](https://developer.atlassian.com/server/framework/atlassian-sdk/web-section-plugin-module/#condition-and-conditions-elements) and check the [documentation of `conditionMap` option from `@atlassian/webresource-webpack-plugin`](https://www.npmjs.com/package/@atlassian/webresource-webpack-plugin#conditionmap-optional).
 
 ```ts
 import { LinkExtension } from '@atlassian/clientside-extensions';
@@ -327,7 +327,7 @@ import { LinkExtension } from '@atlassian/clientside-extensions';
 export default LinkExtension.factory(/*...*/);
 ```
 
-These `@condition` annotations will result in creating a condition map object that is matching the [shape of `conditionMap` option from `atlassian-webresource-webpack-plugin`](https://www.npmjs.com/package/atlassian-webresource-webpack-plugin#conditionmap-optional):
+These `@condition` annotations will result in creating a condition map object that is matching the [shape of `conditionMap` option from `@atlassian/webresource-webpack-plugin`](https://www.npmjs.com/package/@atlassian/webresource-webpack-plugin#conditionmap-optional):
 
 ```json
 {
@@ -376,7 +376,7 @@ import { LinkExtension } from '@atlassian/clientside-extensions';
 export default LinkExtension.factory(/*...*/);
 ```
 
-These `@condition` annotations will result in creating a condition map object that is matching the [shape of `conditionMap` option from `atlassian-webresource-webpack-plugin`](https://www.npmjs.com/package/atlassian-webresource-webpack-plugin#conditionmap-optional):
+These `@condition` annotations will result in creating a condition map object that is matching the [shape of `conditionMap` option from `@atlassian/webresource-webpack-plugin`](https://www.npmjs.com/package/@atlassian/webresource-webpack-plugin#conditionmap-optional):
 
 ```json
 {

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

@@ -4,12 +4,12 @@ platform: server
 product: clientside-extensions
 category: reference
 subcategory: webpack
-date: '2024-09-24'
+date: '2025-06-08'
 ---
 
 # Webpack plugin
 
-Client-side Extensions webpack plugin depends on [WRM webpack plugin](https://www.npmjs.com/package/atlassian-webresource-webpack-plugin).
+Client-side Extensions webpack plugin depends on [WRM webpack plugin](https://www.npmjs.com/package/@atlassian/webresource-webpack-plugin).
 
 Refer to the [setup guide](/server/framework/clientside-extensions/guides/how-to/setup-webpack-plugin/) to check how to install and configure the webpack plugin.
 
@@ -53,7 +53,7 @@ Generates all the entry-point definitions for the webpack `entry` configuration.
 ```js
 const path = require('path');
 const ClientsideExtensionsWebpackPlugin = require('@atlassian/clientside-extensions-webpack-plugin');
-const WrmPlugin = require('atlassian-webresource-webpack-plugin');
+const WrmPlugin = require('@atlassian/webresource-webpack-plugin');
 
 const wrmPlugin = new WrmPlugin(/*...*/);
 

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@atlassian/clientside-extensions-docs",
-    "version": "5.0.0",
+    "version": "5.1.0-9864e593-me132vr9",
     "description": "Holds the official documentation for Altassian Server client-side extensions API.",
     "license": "BSD-3-Clause",
     "homepage": "https://bitbucket.org/atlassian/atlassian-clientside-extensions#readme",
@@ -48,7 +48,7 @@
     ],
     "publishConfig": {
         "access": "public",
-        "@atlassian:registry": "https://registry.npmjs.org/"
+        "@atlassian:registry": "https://packages.atlassian.com/api/npm/npm-public/"
     },
     "docs": [
         {
@@ -77,8 +77,8 @@
         "//comment": "We use the proxy command to 'doc-scripts' so we don't need to pass the enviroment flag all over the places",
         "doc-scripts": "env SKIP_VERSION_CHECK=true doc-scripts"
     },
-    "optionalDependencies": {
+    "devDependencies": {
         "@atlassian/doc-scripts": "^11.1.0"
     },
-    "gitHead": "797ed863b536adc5806a0f9438ee9501d710a467"
+    "gitHead": "9864e5937d68e51d7a26eece1238be16589135b5"
 }