Merge pull request #1815 from spryker/bugfix/supesc-690-move-overridi…

…ng-webpack-zed-to-includes

Overriding Webpack, JS, SCSS for ZED on project level

_includes/scos/dev/front-end-development/zed/202212.0/overriding-webpack-js-scss-for-zed-on-project-level.md

@@ -0,0 +1,137 @@
+
+
+To override or expand core JS, SCSS, you need to expand the `oryx-for-zed` building system with an additional config:
+
+* To adjust the Webpack config and create aliases for core modules, see [Webpack](#webpack).
+* To create a new entry point and file naming and extend core JS files and path for entry points, see [JS](#js).
+* To create a new file with styles and build it with Webpack, see [SCSS](#scss).
+* To add output JS and CSS on a page, see [TWIG](#twig).
+
+## Webpack
+
+Create a new javascript file in `./frontend/zed/build.js`. Copy the code below to the file:
+
+```js
+const oryx = require('@spryker/oryx');
+const oryxForZed = require('@spryker/oryx-for-zed');
+const copyAssets = require('@spryker/oryx-for-zed/lib/copy');
+const path = require('path');
+const merge = require('webpack-merge');
+
+const mergeWithStrategy = merge.smartStrategy({
+    plugins: 'prepend'
+});
+
+const myCustomZedSettings = mergeWithStrategy(oryxForZed.settings, {
+    entry: {
+        dirs: [path.resolve('./src/Pyz/Zed/')] // Path for entry points on project level
+    }
+});
+
+oryxForZed.getConfiguration(myCustomZedSettings)
+	.then(configuration => oryx.build(configuration, copyAssets))
+	.catch(error => console.error('An error occurred while creating configuration', error));
+```
+
+The `oryx-for-zed` building settings must be expanded with a path to ZED modules on the project level (`entry.dirs`). 
+Due to `mergeWithStrategy`, the default config with core paths is expanded with a path to the project level.
+
+{% info_block infoBox %}
+
+Use `merge` from Webpack (see the example above) instead  of `Object.assign(…)`. If you use `Object.assign(…)`, the entry points config will be fully overwritten.
+
+{% endinfo_block %}
+
+If new packages have been installed for modules through `npm`, specify the path to the `resolveModules` option on the project level.
+
+Example:
+
+```js
+const myCustomZedSettings = mergeWithStrategy(oryxForZed.settings, {
+    ...,
+    resolveModules: {
+        dirs: [path.resolve('./src/Pyz/Zed/')]
+    }
+});
+```
+
+After creating the new build for ZED, specify the new commands in root `package.json`. 
+
+Example:
+
+```js
+{
+    scripts: {
+        "zed": "node ./frontend/zed/build",
+        "zed:watch": "node ./frontend/zed/build --dev",
+        "zed:production": "node ./frontend/zed/build --prod"
+    }
+}
+```
+
+### Aliases
+
+To extend the core JS, there should be Webpack aliases for the core modules. To make the new aliases available, extend the Webpack configuration with the new aliases:
+
+```js
+oryxForZed.getConfiguration(myCustomZedSettings).then(configuration => oryx.build(mergeWithStrategy(configuration, {
+    resolve: {
+        alias: {
+            {% raw %}{%{% endraw %}AliasName{% raw %}%}{% endraw %}: 'path/to/module/assets' // Example: 'Gui/assets/Zed/js/**'
+        }
+    }
+})));
+```
+
+{% info_block infoBox %}
+
+You can check the existing list of aliases in the [webpack.config.js](https://github.com/spryker/oryx-for-zed/blob/master/lib/webpack.config.js#L57) file of `oryx-for-zed`.
+
+{% endinfo_block %}
+
+## JS
+
+The newly created entry points for JS files should have the suffix `.entry` — for example, `my-module.entry.js`). Webpack collects all entry points with this suffix.
+
+Use the following path to add all new entry points for your project: `./src/Pyz/Zed/{% raw %}{%{% endraw %}ModuleName{% raw %}%}{% endraw %}/assets/Zed/js/*.entry.js`.
+
+To extend JS modules from the core level, use [aliases](#aliases). 
+
+To add a JS module, follow the example:
+
+```js
+require('{% raw %}{%{% endraw %}AliasName{% raw %}%}{% endraw %}/path/to/file.js');
+// OR
+var ModuleName = require('{% raw %}{%{% endraw %}AliasName{% raw %}%}{% endraw %}/path/to/file.js');
+```
+
+## SCSS
+
+Use the following path to add all files with style: `./src/Pyz/Zed/{% raw %}{%{% endraw %}ModuleName{% raw %}%}{% endraw %}/assets/Zed/sass/*.scss`. Webpack collects only those styles that were provided in the entry point (JS).
+
+Add style files by following the example:
+
+```js
+require('path/to/file.scss') // Example: '../sass/*.scss'
+```
+
+{% info_block infoBox %}
+
+The generated CSS file has the same naming as the JS entry point. For example, if a JS entry point's name is `spryker-gui.entry.js`, the CSS output is `spryker-gui.css`.
+
+{% endinfo_block %}
+
+## TWIG
+
+Webpack generates each entry point as a separate JS file. If the JS file is not added to the TWIG JS, it won’t work.
+Keep in mind, that the file generated by Webpack JS doesn’t have an `.entry` suffix. For example, instead of `module-name.entry.js`, the name is `module-name.js`: 
+
+```js
+<script src="{% raw %}{{{% endraw %} assetsPath('js/*.js') {% raw %}}}{% endraw %}"></script>
+```
+
+The newly generated styles have to be added to the twig template too. Note that Webpack automatically renames the output css files with the JS entry point name:
+
+```js
+<link rel="stylesheet" href="{% raw %}{{{% endraw %} assetsPath('css/*.css') {% raw %}}}{% endraw %}">
+```

_includes/scos/dev/front-end-development/zed/202304.0/overriding-webpack-js-scss-for-zed-on-project-level.md

@@ -0,0 +1,147 @@
+
+
+To override or expand core JS, SCSS, you need to expand the `oryx-for-zed` building system with an additional config:
+
+* To adjust the Webpack config and create aliases for core modules, see [Webpack](#webpack). 
+* To create a new entry point and file naming and extend core JS files and path for entry points, see [JS](#js). 
+* To create a new file with styles and build it with Webpack, see [SCSS](#scss).
+* To add output JS and CSS on a page, see [TWIG](#twig).
+
+## Webpack
+
+{% info_block infoBox %}
+
+The minimum required versions: 
+
+- `@spryker/oryx-for-zed`: 2.13.0
+- `webpack`: 5.*
+- `webpack-merge`: 5.*
+
+{% endinfo_block %}
+
+Create a new javascript file in `./frontend/zed/build.js`. Copy the code below to the file:
+
+```js
+const { mergeWithCustomize, customizeObject } = require('webpack-merge');
+const oryxForZed = require('@spryker/oryx-for-zed');
+const path = require('path');
+
+const mergeWithStrategy = mergeWithCustomize({
+    customizeObject: customizeObject({
+        plugins: 'prepend'
+    })
+});
+
+const myCustomZedSettings = mergeWithStrategy(oryxForZed.settings, {
+    entry: {
+        dirs: [path.resolve('./src/Pyz/Zed/')] // Path for entry points on project level
+    }
+});
+
+oryxForZed.getConfiguration(myCustomZedSettings)
+    .then(configuration => oryxForZed.build(configuration, oryxForZed.copyAssets))
+    .catch(error => console.error('An error occurred while creating configuration', error));
+```
+
+The `oryx-for-zed` building settings must be expanded with a path to ZED modules on the project level (`entry.dirs`). 
+Due to `mergeWithStrategy`, the default config with core paths is expanded with a path to the project level.
+
+{% info_block infoBox %}
+
+Use `mergeWithCustomize` from Webpack (see the preceding example) instead of `Object.assign(…)`. If you use `Object.assign(…)`, the entry points config gets fully overwritten.
+
+{% endinfo_block %}
+
+If new packages have been installed for modules through `npm`, specify the path to the `resolveModules` option on the project level.
+
+Example:
+
+```js
+const myCustomZedSettings = mergeWithStrategy(oryxForZed.settings, {
+    ...,
+    resolveModules: {
+        dirs: [path.resolve('./src/Pyz/Zed/')]
+    }
+});
+```
+
+After creating the new build for ZED, specify the new commands in root `package.json`. 
+
+Example:
+
+```js
+{
+    scripts: {
+        "zed":"node ./frontend/zed/build",
+        "zed:watch":"node ./frontend/zed/build --dev",
+        "zed:production":"node ./frontend/zed/build --prod"
+    }
+}
+```
+
+### Aliases
+
+To extend the core JS, there must be Webpack aliases for the core modules. To make the new aliases available, extend the Webpack configuration with the new aliases:
+
+```js
+oryxForZed.getConfiguration(myCustomZedSettings).then(configuration => oryxForZed.build(mergeWithStrategy(configuration, {
+    resolve: {
+        alias: {
+            {% raw %}{%{% endraw %}AliasName{% raw %}%}{% endraw %}: 'path/to/module/assets' // Example: 'Gui/assets/Zed/js/**'
+        }
+    }
+})));
+```
+
+{% info_block infoBox %}
+
+You can check the existing list of aliases in the [webpack.config.js](https://github.com/spryker/oryx-for-zed/blob/master/lib/webpack.config.js#L57) file of `oryx-for-zed`.
+
+{% endinfo_block %}
+
+## JS
+
+The newly created entry points for JS files should have the suffix `.entry` — for example, `my-module.entry.js`. Webpack collects all entry points with this suffix.
+
+Use the following path to add all new entry points for your project: `./src/Pyz/Zed/{% raw %}{%{% endraw %}ModuleName{% raw %}%}{% endraw %}/assets/Zed/js/*.entry.js`.
+
+To extend JS modules from the core level, use [aliases](#aliases).
+
+To add a JS module, follow the example:
+
+```js
+require('{% raw %}{%{% endraw %}AliasName{% raw %}%}{% endraw %}/path/to/file.js');
+// OR
+var ModuleName = require('{% raw %}{%{% endraw %}AliasName{% raw %}%}{% endraw %}/path/to/file.js');
+```
+
+## SCSS
+
+Use the following path to add all files with style: `./src/Pyz/Zed/{% raw %}{%{% endraw %}ModuleName{% raw %}%}{% endraw %}/assets/Zed/sass/*.scss`. Webpack collects only styles provided in the entry point (JS).
+
+Add style files by following the example:
+
+```js
+require('path/to/file.scss') // Example: '../sass/*.scss'
+```
+
+{% info_block infoBox %}
+
+The generated CSS file has the same naming as the JS entry point. For example, if a JS entry point's name is `spryker-gui.entry.js`, the CSS output is `spryker-gui.css`.
+
+{% endinfo_block %}
+
+## TWIG
+
+Webpack generates each entry point as a separate JS file. If the JS file is not added to the TWIG JS, it won't work.
+Keep in mind, that the file generated by Webpack JS doesn't have an `.entry` suffix. For example, instead of `module-name.entry.js`, the name is `module-name.js`:
+
+```html
+<script src="{% raw %}{{{% endraw %} assetsPath('js/*.js') {% raw %}}}{% endraw %}"></script>
+```
+
+The newly generated styles have to be added to the twig template too. Note that Webpack automatically renames the output CSS files with the JS entry point name:
+
+```html
+<link rel="stylesheet" href="{% raw %}{{{% endraw %} assetsPath('css/*.css') {% raw %}}}{% endraw %}">
+```