babylon - npm Package Compare versions

Comparing version 7.0.0-beta.46 to 7.0.0-beta.47

package.json

 {
   "name": "babylon",
-  "version": "7.0.0-beta.46",
+  "version": "7.0.0-beta.47",
   "description": "A JavaScript parser",
@@ -26,3 +26,3 @@ "author": "Sebastian McKenzie <[e-mail]>",
   "devDependencies": {
-    "@babel/helper-fixtures": "7.0.0-beta.46",
+    "@babel/helper-fixtures": "7.0.0-beta.47",
     "charcodes": "0.1.0",
@@ -29,0 +29,0 @@ "unicode-10.0.0": "^0.7.4"

README.md

@@ -155,3 +155,3 @@ <p align="center">
 
-We currently aren't willing to commit to supporting the API for plugins or the resulting ecosystem (there is already enough work maintaining Babel's own plugin system). It's not clear how to make that API effective, and it would limit out ability to refactor and optimize the codebase.
+We currently aren't willing to commit to supporting the API for plugins or the resulting ecosystem (there is already enough work maintaining Babel's own plugin system). It's not clear how to make that API effective, and it would limit our ability to refactor and optimize the codebase.
 
@@ -158,0 +158,0 @@ Our current recommendation for those that want to create their own custom syntax is for users to fork Babylon.

Fixed alerts

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

Improved metrics

Total package byte prevSize

372815

increased by0.46%

Lines of code

8238

increased by0.51%

Number of medium supply chain risk alerts

0

decreased by-100%

No dependency changes