@financial-times/o-syntax-highlight - npm Package Compare versions

Comparing version 4.0.0-beta.0 to 4.0.0

MIGRATION.md

 ## Migration Guide
 
+### Migrating from v3 to v4
+
+V4 has dropped support for use through Bower. If you have been using Bower, you will need to follow the [bower to npm migration guide](https://origami.ft.com/docs/tutorials/bower-to-npm/).
+
+When using Sass, you will need to add `node_modules` to your `includePath` as well as either:
+
+- Update your code to use the fully qualified package name, i.e.: `@import "@financial-times/o-brand/main"`, or
+- Also add `node_modules/@financial-times` to the Sass include path
+
+
 ### Migrating from v2 to v3
@@ -4,0 +14,0 @@

package.json

 {
 	"name": "@financial-times/o-syntax-highlight",
-	"version": "4.0.0-beta.0",
+	"version": "4.0.0",
 	"description": "A syntax highlighter for Origami-supported documentation that wraps PrismJs",
@@ -18,3 +18,3 @@ "keywords": [
 		"start": "npx serve ./demos/local",
-		"build": "npm_config_yes=true npx \"origami-build-tools@prerelease\" install && npm_config_yes=true npx \"origami-build-tools@prerelease\" demo"
+		"build": "npm_config_yes=true npx \"origami-build-tools@11\" install && npm_config_yes=true npx \"origami-build-tools@11\" demo"
 	},
@@ -26,3 +26,3 @@ "devDependencies": {
 		"remark-lint": "^7.0.1",
-		"remark-preset-lint-origami-component": "prerelease",
+		"remark-preset-lint-origami-component": "^2.0.0",
 		"stylelint": "^13.12.0",
@@ -35,3 +35,3 @@ "stylelint-config-origami-component": "^1.0.4"
 	"peerDependencies": {
-		"@financial-times/o-colors": "prerelease"
+		"@financial-times/o-colors": "^6.0.0"
 	},
@@ -38,0 +38,0 @@ "engines": {

README.md

@@ -156,4 +156,5 @@ # o-syntax-highlight
 :---: | :---: | :---: | :---:
-✨ active | 3 | N/A | [migrate to v3](MIGRATION.md#migrating-from-v2-to-v3) |
-⚠ maintained | 2 | 2.1 | [migrate to v2](MIGRATION.md#migrating-from-v1-to-v2) |
+✨ active | 3 | N/A | [migrate to v4](MIGRATION.md#migrating-from-v3-to-v4) |
+⚠ maintained | 3 | 3.0 | [migrate to v3](MIGRATION.md#migrating-from-v2-to-v3) |
+╳ deprecated | 2 | 2.1 | [migrate to v2](MIGRATION.md#migrating-from-v1-to-v2) |
 ╳ deprecated | 1 | 1.6.4 | N/A |
@@ -160,0 +161,0 @@

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

No v1

Quality

Package is not semver >=1. This means it is not stable and does not support ^ ranges.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

32813

increased by1.7%

Number of low quality alerts

1

decreased by-50%

Number of lines in readme file

169

increased by0.6%

Worsened metrics

Number of medium supply chain risk alerts

1

increased byInfinity%

No dependency changes