@storm-software/workspace-tools 1.5.9 → 1.5.11

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.
package/CHANGELOG.md CHANGED
@@ -1,3 +1,18 @@
1
+ ## [1.5.10](https://github.com/storm-software/storm-ops/compare/workspace-tools-v1.5.9...workspace-tools-v1.5.10) (2023-11-08)
2
+
3
+
4
+ ### Bug Fixes
5
+
6
+ * **create-storm-workspace:** Updated vsc setting config and args order ([0cdbfef](https://github.com/storm-software/storm-ops/commit/0cdbfef3083d2fbc3a2b65c185d2c5ac61ce0207))
7
+ * **workspace-tools:** Resolved issue with Setup Workspace action name ([1ccd8b4](https://github.com/storm-software/storm-ops/commit/1ccd8b4f0523576175e48ef36cfa4a47f00e4ad4))
8
+
9
+ ## [1.5.9](https://github.com/storm-software/storm-ops/compare/workspace-tools-v1.5.8...workspace-tools-v1.5.9) (2023-11-08)
10
+
11
+
12
+ ### Bug Fixes
13
+
14
+ * **workspace-tools:** Updated package.json scripts in preset ([9dd9b9c](https://github.com/storm-software/storm-ops/commit/9dd9b9cc2acd250da5e8278d7ef2212aff6469f6))
15
+
1
16
  ## [1.5.8](https://github.com/storm-software/storm-ops/compare/workspace-tools-v1.5.7...workspace-tools-v1.5.8) (2023-11-08)
2
17
 
3
18
 
package/README.md CHANGED
@@ -15,7 +15,7 @@ This package is part of the <b>⚡Storm-Ops</b> monorepo. The Storm-Ops packages
15
15
 
16
16
  <h3 align="center">💻 Visit <a href="https://stormsoftware.org" target="_blank">stormsoftware.org</a> to stay up to date with this developer</h3><br />
17
17
 
18
- [![Version](https://img.shields.io/badge/version-1.5.3-1fb2a6.svg?style=for-the-badge&color=1fb2a6)](https://prettier.io/)&nbsp;
18
+ [![Version](https://img.shields.io/badge/version-1.5.9-1fb2a6.svg?style=for-the-badge&color=1fb2a6)](https://prettier.io/)&nbsp;
19
19
  [![Nx](https://img.shields.io/badge/Nx-17.0.2-lightgrey?style=for-the-badge&logo=nx&logoWidth=20&&color=1fb2a6)](http://nx.dev/)&nbsp;[![NextJs](https://img.shields.io/badge/Next.js-14.0.2-lightgrey?style=for-the-badge&logo=nextdotjs&logoWidth=20&color=1fb2a6)](https://nextjs.org/)&nbsp;[![Commitizen friendly](https://img.shields.io/badge/commitizen-friendly-brightgreen.svg?style=for-the-badge&logo=commitlint&color=1fb2a6)](http://commitizen.github.io/cz-cli/)&nbsp;![Semantic-Release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg?style=for-the-badge&color=1fb2a6)&nbsp;[![documented with docusaurus](https://img.shields.io/badge/documented_with-docusaurus-success.svg?style=for-the-badge&logo=readthedocs&color=1fb2a6)](https://docusaurus.io/)&nbsp;![GitHub Workflow Status (with event)](https://img.shields.io/github/actions/workflow/status/storm-software/storm-ops/cr.yml?style=for-the-badge&logo=github-actions&color=1fb2a6)
20
20
 
21
21
  <h3 align="center" bold="true">⚠️ <b>Attention</b> ⚠️ - This repository, and the apps, libraries, and tools contained within, is still in it's initial development phase. As a result, bugs and issues are expected with it's usage. When the main development phase completes, a proper release will be performed, the packages will be availible through NPM (and other distributions), and this message will be removed. However, in the meantime, please feel free to report any issues you may come across.</h3><br />
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@storm-software/workspace-tools",
3
- "version": "1.5.9",
3
+ "version": "1.5.11",
4
4
  "private": false,
5
5
  "description": "⚡ A Nx plugin package that contains various executors and generators used in a Storm workspaces.",
6
6
  "keywords": [
@@ -7,6 +7,9 @@
7
7
  "README.md"
8
8
  ],
9
9
  "imageSize": 100,
10
+ "contributorsPerLine": 5,
11
+ "linkToUsage": true,
12
+ "commitType": "docs"
10
13
  "commit": true,
11
14
  "commitConvention": "angular",
12
15
  "contributors": [
@@ -41,8 +44,5 @@
41
44
  "maintenance"
42
45
  ]
43
46
  }
44
- ],
45
- "contributorsPerLine": 7,
46
- "linkToUsage": true,
47
- "commitType": "docs"
47
+ ]
48
48
  }
@@ -0,0 +1,32 @@
1
+ ## VS Code Settings
2
+
3
+ This directory includes the global settings for the development of this Storm workspace.
4
+
5
+ See:
6
+
7
+ - [VS Code Doc: User and Workspace Settings](https://code.visualstudio.com/docs/getstarted/settings)
8
+ - [What is a VS Code Workspace?](https://stackoverflow.com/questions/44629890/what-is-a-workspace-in-visual-studio-code)
9
+
10
+ ### Overriding Global Settings
11
+
12
+ It is possible to create your own "local" settings, overriding the global, via a `.code-workspace` file. See:
13
+
14
+ - [Workspace Settings](https://code.visualstudio.com/docs/editor/multi-root-workspaces#_settings)
15
+ - [Local settings overrides](https://github.com/microsoft/vscode/issues/37519)
16
+
17
+ > `*.code-workspace` files are included in `.gitignore`
18
+
19
+ For example, if you want a bright pink status background (and who doesn't?), create this file in the root of your project `mySettings.code-workspace`:
20
+
21
+ ```
22
+ // mySettings.code-workspace
23
+
24
+ "workbench.colorCustomizations": {
25
+ "statusBar.background": "#ff007f",
26
+ },
27
+
28
+ ```
29
+
30
+ > **WARNING:** If you create a custom file that is ignored by git, then _anytime_ you run `git clean -fxd` the file will be permanently deleted.
31
+ >
32
+ > You can avoid this by using the option `-e`, e.g. `git clean -fxd -e mySettings.code-workspace`.
@@ -18,6 +18,20 @@
18
18
  "**/dist": true
19
19
  },
20
20
 
21
+ /******************************
22
+ * VS Code colorization
23
+ ******************************/
24
+ "workbench.colorCustomizations": {
25
+ "statusBar.background": "#1d232a",
26
+ "statusBarItem.hoverBackground": "#313C47",
27
+ "statusBar.foreground": "#1fb2a6"
28
+ },
29
+
30
+ /******************************
31
+ * Peacock colorization
32
+ ******************************/
33
+ "peacock.color": "#1fb2a6",
34
+
21
35
  /******************************
22
36
  * bracket pair colorization
23
37
  ******************************/
@@ -1,123 +0,0 @@
1
- name: "Web App Bundle Analysis"
2
-
3
- on:
4
- push:
5
- branches:
6
- - main
7
- pull_request:
8
- branches:
9
- - main
10
- workflow_dispatch:
11
-
12
- defaults:
13
- run:
14
- # change this if your nextjs app does not live at the root of the repo
15
- working-directory: ./
16
-
17
- env:
18
- CI: true
19
- NX_DAEMON: false
20
- NX_VERBOSE_LOGGING: true
21
- SKIP_ENV_VALIDATION: true
22
- ANALYZE: true
23
-
24
- jobs:
25
- analyze:
26
- runs-on: ubuntu-latest
27
- steps:
28
- - uses: actions/checkout@v4
29
- with:
30
- fetch-depth: 0
31
- token: ${{ secrets.STORMIE_GITHUB_TOKEN }}
32
-
33
- - name: Setup workspace
34
- uses: ./.github/actions/setup-workspace
35
-
36
- - name: Restore next build
37
- uses: actions/cache@v3
38
- id: restore-build-cache
39
- env:
40
- cache-name: cache-next-build
41
- with:
42
- path: dist/apps/web/app/.next/cache
43
- # change this if you prefer a more strict cache
44
- key: ${{ runner.os }}-build-${{ env.cache-name }}
45
-
46
- - name: Build next.js app
47
- run: pnpm nx run web-app:build
48
- env:
49
- SKIP_BUILD_PRODUCT_REDIRECTS: 1
50
- ANALYZE: true
51
-
52
- # Here's the first place where next-bundle-analysis' own script is used
53
- # This step pulls the raw bundle stats for the current bundle
54
- - name: Analyze bundle
55
- run: pnpm -p nextjs-bundle-analysis report
56
- env:
57
- ANALYZE: true
58
-
59
- - name: Upload bundle
60
- uses: actions/upload-artifact@v3
61
- with:
62
- name: bundle
63
- path: dist/apps/web/app/.next/analyze/__bundle_analysis.json
64
-
65
- #- name: Download base branch bundle stats
66
- # uses: dawidd6/action-download-artifact@v2
67
- # if: success() && github.event.number
68
- # with:
69
- # workflow: nextjs_bundle_analysis.yml
70
- # branch: ${{ github.event.pull_request.base.ref }}
71
- # path: dist/apps/web/shell/.next/analyze/base
72
-
73
- # And here's the second place - this runs after we have both the current and
74
- # base branch bundle stats, and will compare them to determine what changed.
75
- # There are two configurable arguments that come from package.json:
76
- #
77
- # - budget: optional, set a budget (bytes) against which size changes are measured
78
- # it's set to 350kb here by default, as informed by the following piece:
79
- # https://infrequently.org/2021/03/the-performance-inequality-gap/
80
- #
81
- # - red-status-percentage: sets the percent size increase where you get a red
82
- # status indicator, defaults to 20%
83
- #
84
- # Either of these arguments can be changed or removed by editing the `nextBundleAnalysis`
85
- # entry in your package.json file.
86
- #- name: Compare with base branch bundle
87
- # if: success() && github.event.number
88
- # run: ls -laR dist/apps/web/shell/.next/analyze/base && npx -p nextjs-bundle-analysis compare
89
-
90
- #- name: Get comment body
91
- # id: get-comment-body
92
- # if: success() && github.event.number
93
- # uses: actions/github-script@v6
94
- # with:
95
- # result-encoding: string
96
- # script: |
97
- # const fs = require('fs')
98
- # const comment = fs.readFileSync('dist/apps/web/shell/.next/analyze/__bundle_analysis_comment.txt', 'utf8')
99
- # core.setOutput('body', comment)
100
-
101
- #- name: Find Comment
102
- # uses: peter-evans/find-comment@v2
103
- # if: success() && github.event.number
104
- # id: fc
105
- # with:
106
- # issue-number: ${{ github.event.number }}
107
- # body-includes: "<!-- __NEXTJS_BUNDLE -->"
108
-
109
- #- name: Create Comment
110
- # uses: peter-evans/create-or-update-comment@v3
111
- # if: success() && github.event.number && steps.fc.outputs.comment-id == 0
112
- # with:
113
- # issue-number: ${{ github.event.number }}
114
- # body: ${{ steps.get-comment-body.outputs.body }}
115
-
116
- #- name: Update Comment
117
- # uses: peter-evans/create-or-update-comment@v3
118
- # if: success() && github.event.number && steps.fc.outputs.comment-id != 0
119
- # with:
120
- # issue-number: ${{ github.event.number }}
121
- # body: ${{ steps.get-comment-body.outputs.body }}
122
- # comment-id: ${{ steps.fc.outputs.comment-id }}
123
- # edit-mode: replace