@ministryofjustice/hmpps-connect-dps-shared-items 5.2.1 → 5.3.1

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/README.md CHANGED
@@ -1,7 +1,8 @@
1
1
  # hmpps-connect-dps-shared-items
2
2
 
3
- [![repo standards badge](https://img.shields.io/badge/endpoint.svg?&style=flat&logo=github&url=https%3A%2F%2Foperations-engineering-reports.cloud-platform.service.justice.gov.uk%2Fapi%2Fv1%2Fcompliant_public_repositories%2Fhmpps-connect-dps-shared-items-package)](https://operations-engineering-reports.cloud-platform.service.justice.gov.uk/public-report/hmpps-connect-dps-shared-items-package "Link to report")
3
+ [![Ministry of Justice Repository Compliance Badge](https://github-community.service.justice.gov.uk/repository-standards/api/hmpps-connect-dps-shared-items-package/badge?style=flat)](https://github-community.service.justice.gov.uk/repository-standards/hmpps-connect-dps-shared-items-package)
4
4
  [![Test, lint & publish](https://github.com/ministryofjustice/hmpps-connect-dps-shared-items-package/actions/workflows/pipeline.yml/badge.svg?branch=main)](https://github.com/ministryofjustice/hmpps-connect-dps-shared-items-package/actions/workflows/pipeline.yml)
5
+ ![NPM version](https://img.shields.io/npm/v/%40ministryofjustice%2Fhmpps-connect-dps-shared-items)
5
6
 
6
7
  A library for sharing DPS Components across applications.
7
8
 
@@ -30,7 +31,7 @@ Add the `hmpps-connect-dps-shared-items` assets directory to nunjucks configurat
30
31
  const njkEnv = nunjucks.configure(
31
32
  [
32
33
  path.join(__dirname, '../../server/views'),
33
- ...,
34
+ // ...,
34
35
  'node_modules/@ministryofjustice/hmpps-connect-dps-shared-items/dist/assets/',
35
36
  ],
36
37
  {
@@ -48,11 +49,11 @@ then import the component into your nunjucks file:
48
49
  ### Styling
49
50
  Include the package scss within the `index.scss` file. You can either import all:
50
51
  ```scss
51
- @import 'node_modules/@ministryofjustice/hmpps-connect-dps-shared-items/dist/assets/scss/all';
52
+ @use 'node_modules/@ministryofjustice/hmpps-connect-dps-shared-items/dist/assets/scss/all';
52
53
  ```
53
54
  or import the specific component scss you are using, e.g:
54
55
  ```scss
55
- @import 'node_modules/@ministryofjustice/hmpps-connect-dps-shared-items/dist/assets/dps/components/alert-flag/alert-flag';
56
+ @use 'node_modules/@ministryofjustice/hmpps-connect-dps-shared-items/dist/assets/dps/components/alert-flag/alert-flag';
56
57
  ```
57
58
 
58
59
  ### Client side javascript
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ministryofjustice/hmpps-connect-dps-shared-items",
3
- "version": "5.2.1",
3
+ "version": "5.3.1",
4
4
  "description": "A package to share Connect DPS functionality across applications",
5
5
  "main": "./dist/index.cjs",
6
6
  "module": "./dist/index.esm.js",
@@ -25,7 +25,7 @@
25
25
  "precommit:secrets": "gitleaks git --pre-commit --redact --staged --verbose --config .gitleaks/config.toml",
26
26
  "precommit:lint": "lint-staged",
27
27
  "precommit:verify": "npm run typecheck && npm test",
28
- "setup": "npm ci && hmpps-npm-script-run-allowlist",
28
+ "setup": "npm clean-install",
29
29
  "start": "node --experimental-strip-types preview/server.mts"
30
30
  },
31
31
  "lint-staged": {
@@ -49,8 +49,8 @@
49
49
  },
50
50
  "devDependencies": {
51
51
  "@ministryofjustice/eslint-config-hmpps": "2.0.0-alpha.2",
52
+ "@ministryofjustice/frontend": "11.1.0",
52
53
  "@ministryofjustice/frontend-types": "2.0.2",
53
- "@ministryofjustice/hmpps-npm-script-allowlist": "0.0.6",
54
54
  "@ministryofjustice/hmpps-precommit-hooks": "3.0.2",
55
55
  "@rollup/plugin-commonjs": "^29.0.3",
56
56
  "@rollup/plugin-multi-entry": "^7.1.0",
@@ -60,34 +60,38 @@
60
60
  "@types/jest": "^30.0.0",
61
61
  "@types/nunjucks": "3.2.6",
62
62
  "@types/superagent": "^8.1.11",
63
- "govuk-frontend": "6.4.0",
63
+ "govuk-frontend": "6.5.1",
64
64
  "jest": "^30.4.2",
65
65
  "jest-html-reporter": "^4.4.0",
66
66
  "jest-junit": "^17.0.0",
67
67
  "lint-staged": "^17.2.0",
68
68
  "nock": "14.0.17",
69
69
  "nunjucks": "3.2.4",
70
- "rollup": "4.63.0",
70
+ "rollup": "4.63.5",
71
71
  "rollup-plugin-copy": "3.5.0",
72
72
  "rollup-plugin-dts": "6.5.1",
73
73
  "rollup-plugin-scss": "4.0.1",
74
- "sass": "1.103.1",
75
- "ts-jest": "29.4.12",
74
+ "sass": "1.105.0",
75
+ "ts-jest": "29.4.14",
76
76
  "tslib": "^2.8.1",
77
77
  "typescript": "6.0.3"
78
78
  },
79
79
  "dependencies": {
80
- "@ministryofjustice/frontend": "11.0.0",
81
80
  "@ministryofjustice/hmpps-rest-client": "2.2.0",
82
81
  "@types/bunyan": "^1.8.11",
83
82
  "fuse.js": "7.5.0",
84
- "superagent": "10.3.0"
83
+ "superagent": "10.4.1"
85
84
  },
86
85
  "peerDependencies": {
87
- "@ministryofjustice/frontend": "10 | 11",
88
- "govuk-frontend": "^6"
86
+ "@ministryofjustice/frontend": ">=10",
87
+ "govuk-frontend": ">=6.2"
89
88
  },
90
89
  "overrides": {
91
- "brace-expansion": "5.0.9"
90
+ "brace-expansion": ">=5.0.12"
91
+ },
92
+ "allowScripts": {
93
+ "@parcel/watcher@2.6.0": true,
94
+ "fsevents@2.3.3": true,
95
+ "unrs-resolver@1.12.2": true
92
96
  }
93
97
  }
@@ -1,21 +0,0 @@
1
- [< Back](../README.md)
2
- ---
3
-
4
- ## Publishing to NPM
5
-
6
- This library is [published to NPM](https://www.npmjs.com/package/@ministryofjustice/hmpps-connect-dps-components).
7
-
8
- The process to publish a change is as follows:
9
-
10
- * Create a branch from `main`
11
- * Make the code changes
12
- * Run `npm version <patch|minor|major> --no-git-tag-version` to bump the version number appropriately (for help with
13
- semantic versioning, see https://semver.org/)
14
- * Commit the changes, push the branch and raise a PR
15
- * Once the PR has been merged to `main`, [create a new release](https://github.com/ministryofjustice/hmpps-connect-dps-shared-items-package/releases/new):
16
- * Select the `Choose a tag` dropdown and create a new tag entering the new version number (e.g. `0.0.1`)
17
- * Enter the version number as the release title (e.g. `0.0.1`)
18
- * Enter a more detailed description of the release
19
- * Click `Publish release`
20
-
21
- GitHub Actions is configured to trigger on the tagged release and publish to NPM.