update dependencies

.nvmrc

@@ -1 +1 @@
-v18
+v18

package.json

@@ -16,9 +16,9 @@
 		"@babel/cli": "^7.12.10",
 		"@babel/core": "^7.14.2",
 		"@babel/preset-env": "^7.14.2",
-		"@rollup/plugin-commonjs": "^24.0.1",
+		"@rollup/plugin-commonjs": "^25.0.7",
 		"@rollup/plugin-node-resolve": "^15.0.1",
-		"@size-limit/preset-small-lib": "^8.0.1",
+		"@size-limit/preset-small-lib": "^10.0.2",
 		"babel-jest": "^29.0.1",
 		"babel-loader": "^9.1.2",
 		"cartesian": "^1.0.1",
@@ -28,14 +28,14 @@
 		"jest": "^29.0.1",
 		"jest-environment-jsdom": "^29.0.1",
 		"jsdoc-to-markdown": "^8.0.0",
-		"lerna": "^6.0.1",
+		"lerna": "^7.4.2",
 		"lerna-changelog": "^2.2.0",
 		"markdown-toc": "^1.2.0",
-		"prettier": "^2.3.0",
-		"rollup": "^3.2.3",
-		"size-limit": "^8.0.1",
-		"sloc": "^0.2.1",
-		"typescript": "^4.1.3",
+		"prettier": "^3.0.3",
+		"rollup": "^4.3.0",
+		"size-limit": "^10.0.2",
+		"sloc": "^0.3.0",
+		"typescript": "^5.2.2",
 		"webpack": "^5.37.0",
 		"webpack-bundle-analyzer": "^4.8.0",
 		"webpack-cli": "^5.0.1"

packages/chord-symbol-ultimateguitar/yarn.lock

@@ -2,10 +2,10 @@
 # yarn lockfile v1
 
 
-chord-symbol@^4.0.0-beta.1:
-  version "4.0.0-beta.1"
-  resolved "https://registry.yarnpkg.com/chord-symbol/-/chord-symbol-4.0.0-beta.1.tgz#5d844cbfb9b82a30837a5d8ff2d7d7274b81bcba"
-  integrity sha512-aXBhb9PwuMf6KDYYhaiX6JcCzM5ECU77NN3aKXFFzH/CqUrExzUJ8Wez7JC7hHhE4iGtkfmGjsdMsRxB6zYvRQ==
+chord-symbol@^4.0.0:
+  version "4.0.0"
+  resolved "https://registry.yarnpkg.com/chord-symbol/-/chord-symbol-4.0.0.tgz#916603db52b028384991898217be9c89c3bcafdb"
+  integrity sha512-GeECWgVsAAC85G1qpvZo9eLkhfN/9cfX1gD7IXiYFary+JvMIhef3w/Wrm9O6tmjdP5nNeIb3pKDYuA1z25SLg==
   dependencies:
     lodash "^4.17.21"
 

packages/chord-symbol/API.md

@@ -72,7 +72,7 @@ after all built-in filters have been applied.</p>
 For maximum compatibility, your best bet is to always rely on the existing chord object structure.</li>
 <li>To fail the parsing, throw an exception and it will use the Error API.
 If you want to be able to filter your exception in error handling, or to pass the chord object in its current state, use
-<a href="https://github.com/no-chris/chord-symbol/blob/master/src/helpers/ChordParsingError.js">custom error types</a></li>
+<a href="https://github.com/no-chris/chord-symbol/blob/master/packages/chord-symbol/src/helpers/ChordParsingError.js">custom error types</a></li>
 </ul>
 <p><strong>Rendering filter</strong></p>
 <ul>
@@ -547,7 +547,7 @@ after all built-in filters have been applied.
 For maximum compatibility, your best bet is to always rely on the existing chord object structure.
 - To fail the parsing, throw an exception and it will use the Error API.
 If you want to be able to filter your exception in error handling, or to pass the chord object in its current state, use
-[custom error types](https://github.com/no-chris/chord-symbol/blob/master/src/helpers/ChordParsingError.js)
+[custom error types](https://github.com/no-chris/chord-symbol/blob/master/packages/chord-symbol/src/helpers/ChordParsingError.js)
 
 **Rendering filter**
 - If the purpose of your rendering filter is to change the text output of `ChordSymbol`,