reason - npm Package Compare versions

Comparing version 1.11.0 to 1.13.0

package.json

 
 {
-    "version": "1.11.0",
+    "version": "1.13.0",
     "description": "Friendly Syntax & Toolchain Powered by OCaml",
@@ -27,3 +27,3 @@ "repository": {
         "version": {
-            "val": "1.11.0",
+            "val": "1.13.0",
             "global": true,
@@ -46,3 +46,3 @@ "globalCollisionBehavior": "clobber"
             "globalCollisionBehavior": "clobber",
-            "val": "1.11.0"
+            "val": "1.13.0"
         }
@@ -60,3 +60,3 @@ },
         "@opam-alpha/topkg": "0.8.1",
-        "@opam-alpha/ppx_tools_versioned": "5.0.0",
+        "@opam-alpha/reason-parser": "1.13.0",
         "dependency-env": "*",
@@ -69,3 +69,3 @@ "opam-installer-bin": "https://github.com/yunxing/opam-installer-bin.git",
         "editor": "eval $(dependencyEnv) && eval $EDITOR",
-        "postinstall": "eval $(dependencyEnv) && nopam && ./pkg/substs pkg/META.in && make compile_error && make precompile && ./build.native build --native true --native-dynlink true --utop ${utop_installed:-false} && (opam-installer --prefix=$opam_prefix || true)",
+        "postinstall": "eval $(dependencyEnv) && nopam && ./pkg/substs pkg/META.in && make precompile && ./build.native build --native true --native-dynlink true --utop ${utop_installed:-false} && (opam-installer --prefix=$opam_prefix || true)",
         "clean": "eval $(dependencyEnv) && nopam && make clean",
@@ -72,0 +72,0 @@ "env": "eval $(dependencyEnv) && env",

README.md

@@ -109,2 +109,3 @@
 cd reason
+opam pin add -y reason-parser reason-parser
 opam pin add -y reason .
@@ -111,0 +112,0 @@ ```

src/README.md

@@ -15,15 +15,15 @@ # Core Reason
 
-- `reason_config.ml`: global config that says whether our parser should run in "recoverable" mode. Merlin has a neat feature which lets it continue diagnosing e.g. type errors even when the file is syntactically invalid (at the expense of the accuracy of those type error reports' quality). Searching `reason_config` in our codebase will show you how this is used.
+- `reason-parser/src/reason_config.ml`: global config that says whether our parser should run in "recoverable" mode. Merlin has a neat feature which lets it continue diagnosing e.g. type errors even when the file is syntactically invalid (at the expense of the accuracy of those type error reports' quality). Searching `reason_config` in our codebase will show you how this is used.
 
 - `reason_format_type.ml`, `reason_type_of_ocaml_type.ml`: again, see `pkg/build.ml`. These produce the `refmttype` binary, used by [BetterErrors](refmttype) to output compiler errors in Reason syntax rather than the OCaml one.
 
-- `reason_lexer.mll`, `reason_parser.mly`: the tokenizer and the parser! See the first link on Real World OCaml book section. This is used by [Menhir](http://gallium.inria.fr/~fpottier/menhir/), the parser generator.
+- `reason-parser/src/reason_lexer.mll`, `reason_parser.mly`: the tokenizer and the parser! See the first link on Real World OCaml book section. This is used by [Menhir](http://gallium.inria.fr/~fpottier/menhir/), the parser generator.
 
-- `reason_oprint.ml`: the "outcome printer" used by Merlin. No need to worry about it for now.
+- `reason-parser/src/reason_oprint.ml`: the "outcome printer" used by Merlin. No need to worry about it for now.
 
-- `reason_parser.messages`: auto-generated from parser changes. Menhir generates parsing code that assigns each syntax error to a code, and lets us customize these errors. Syntax errors can be very precisely pinpointed and explained this way.
+- `reason-parser/src/reason_parser.messages`: auto-generated from parser changes. Menhir generates parsing code that assigns each syntax error to a code, and lets us customize these errors. Syntax errors can be very precisely pinpointed and explained this way.
 
-- `reason_pprint_ast.ml`: the pretty-printer! This takes in the AST (abstract syntax tree) and prints out the textual code. Theoretically for us, `print (parse myCode) == myCode`.
+- `reason-parser/src/reason_pprint_ast.ml`: the pretty-printer! This takes in the AST (abstract syntax tree) and prints out the textual code. Theoretically for us, `print (parse myCode) == myCode`.
 
-- `reason_toolchain.ml`, `refmt_impl.ml`: the entry point that calls the parsing logic.
+- `reason-parser/src/reason_toolchain.ml`, `refmt_impl.ml`: the entry point that calls the parsing logic.
 
@@ -30,0 +30,0 @@ - `reason_utop.ml`, `reason_toploop.ml`, `rtop_init.ml`: Reason's [Utop](https://github.com/diml/utop) integration. Utop's the terminal-based REPL you see when executing `utop` (in Reason's case, the wrapper `rtop`).

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

Install scripts

Supply chain risk

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Found 1 instance in 1 package

Empty package

Supply chain risk

Package does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.

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

AI-detected potential malware

Supply chain risk

AI has identified this package as malware. This is a strong signal that the package may be malicious.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

1865756

increased by0.86%

Number of package files

138

increased by11.29%

Number of lines in readme file

124

increased by0.81%

Worsened metrics

Lines of code

0

decreased by-100%

Number of medium supply chain risk alerts

3

increased by50%

Dependency changes

• + Added@opam-alpha/reason-parser@1.13.0

• + Added@opam-alpha/reason-parser@1.13.0(transitive)

• - Removed@opam-alpha/ppx_tools_versioned@5.0.0

• - Removed@opam-alpha/ppx_tools_versioned@5.0.0(transitive)