|
@@ -26,7 +26,7 @@ During development, you might find `yarn build:quick` helpful. It is a variant
|
|
of `yarn build` that omits some steps to build a binary quicker, something that
|
|
of `yarn build` that omits some steps to build a binary quicker, something that
|
|
can be useful during development.
|
|
can be useful during development.
|
|
|
|
|
|
-## postinstall
|
|
|
|
|
|
+### postinstall
|
|
|
|
|
|
When using native node modules (those written in C/C++), we need to ensure they
|
|
When using native node modules (those written in C/C++), we need to ensure they
|
|
are built against `electron`'s packaged `node` version. We use
|
|
are built against `electron`'s packaged `node` version. We use
|
|
@@ -34,7 +34,7 @@ are built against `electron`'s packaged `node` version. We use
|
|
to rebuild those modules automatically after each `yarn install` by invoking it
|
|
to rebuild those modules automatically after each `yarn install` by invoking it
|
|
in as the `postinstall` step in our package.json.
|
|
in as the `postinstall` step in our package.json.
|
|
|
|
|
|
-## lint and lint-fix
|
|
|
|
|
|
+### lint and lint-fix
|
|
|
|
|
|
Use `yarn lint` to check that your code formatting is as expected, and that
|
|
Use `yarn lint` to check that your code formatting is as expected, and that
|
|
there are no linter errors. Use `yarn lint-fix` to try and automatically fix the
|
|
there are no linter errors. Use `yarn lint-fix` to try and automatically fix the
|