[Super errors] Update instructions

chenglou · chenglou · commit 3244f868934b · 2021-02-07T08:47:42.000-08:00
No longer need the build cache bursting
diff --git a/jscomp/build_tests/super_errors/README.md b/jscomp/build_tests/super_errors/README.md
@@ -1,13 +1,5 @@
-Special tests for super errors (the pretty error display)
+Special tests for super errors (the pretty error display).
 
-Follow CONTRIBUTING.md and run the integration build that produces the binary needed in these tests:
+Follow CONTRIBUTING.md and build the project, then run `node ./jscomp/build_tests/super_errors/input.js` at the root of the project to check the tests against previous snapshots.
 
-```sh
-npm uninstall -g bs-platform # a cache-busting uninstall is needed, but only for npm >=7
-BS_TRAVIS_CI=1 npm install -g .
-```
-
-To get a production bsc binary the test script will use.
-
-Then, run `node ./jscomp/build_tests/super_errors/input.js` to check the tests against previous snapshots.
-Run `node ./jscomp/build_tests/super_errors/input.js update` to update the snapshots (assuming you've made some changes to super errors' display and/or messages)
+Run `node ./jscomp/build_tests/super_errors/input.js update` to update the snapshots (assuming you've made some changes to super errors' display and/or messages).
diff --git a/jscomp/super_errors/README.md b/jscomp/super_errors/README.md
@@ -1,4 +1,4 @@
-Hello! This is the subdirectory for the new, newcomer-friendly OCaml/Reason warning & error report system. Most of the logic are lifted from the compiler (https://github.com/rescript-lang/ocaml/tree/master). The convention here is to have a `super_foo` for each corresponding compiler's file `foo`. So, for example, `warnings.ml` becomes `super_warnings.ml`. The exception is `super_main`, the entry point.
+Hello! This is the subdirectory for the new, newcomer-friendly ReScript warning & error report system. Most of the logic are lifted from the compiler (https://github.com/rescript-lang/ocaml/tree/master). The convention here is to have a `super_foo` for each corresponding compiler's file `foo`. So, for example, `warnings.ml` becomes `super_warnings.ml`. The exception is `super_main`, the entry point.
 
 Feel free to submit new ones or tweak existing messages in these files! They also have more precise comments in them that tells you how they work.
 

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		-Hello! This is the subdirectory for the new, newcomer-friendly OCaml/Reason warning & error report system. Most of the logic are lifted from the compiler (https://github.com/rescript-lang/ocaml/tree/master). The convention here is to have a `super_foo` for each corresponding compiler's file `foo`. So, for example, `warnings.ml` becomes `super_warnings.ml`. The exception is `super_main`, the entry point.
	`1`	+Hello! This is the subdirectory for the new, newcomer-friendly ReScript warning & error report system. Most of the logic are lifted from the compiler (https://github.com/rescript-lang/ocaml/tree/master). The convention here is to have a `super_foo` for each corresponding compiler's file `foo`. So, for example, `warnings.ml` becomes `super_warnings.ml`. The exception is `super_main`, the entry point.
`2`	`2`
`3`	`3`	`Feel free to submit new ones or tweak existing messages in these files! They also have more precise comments in them that tells you how they work.`
`4`	`4`