@@ -13,7 +13,7 @@ Things that changed:
13
13
## Made it easier to install from source
14
14
15
15
Atom used to have a 5,000 script to prepare a development environment. That also
16
- dependend on older ` npm ` tool - newer ` npm ` versions would crash (and, honestly,
16
+ dependends on older ` npm ` tool - newer ` npm ` versions would crash (and, honestly,
17
17
still are crashing) so we moved away from ` npm ` and are now using ` yarn ` .
18
18
19
19
This is _ not a final decision_ - we just decided for ` yarn ` because newer ` npm `
@@ -29,7 +29,7 @@ sent to our servers, ever. If you're seeing some suspicious requests to servers,
29
29
first try to reproduce on safe mode and if it's still present, please open an
30
30
issue - it may be leftover code that we missed.
31
31
32
- We don't have telemetry andpoints on our backend, and don't intend to have any.
32
+ We don't have telemetry endpoints on our backend, and don't intend to have any.
33
33
34
34
## Library bumps
35
35
@@ -79,7 +79,7 @@ organized](https://github.com/atom/atom/blob/master/script/lib/generate-startup-
79
79
None of these exist on the newer code. This means that _ currently_ Pulsar takes
80
80
more space on the disk _ and_ it's slower to load on some systems. Another weird
81
81
side-effect of the V8 Snapshots is that it allowed Atom to "preload" some code -
82
- sometimes, even ** before** that could could even run! Which means we saw some
82
+ sometimes, even ** before** that could even run! Which means we saw some
83
83
weird bugs appearing that didn't happen on Atom (because some of the stuff that
84
84
should be _ loaded_ in the future was already _ pre-loaded_ because of the
85
85
snapshots), but this, again, made the development process unstable - the source
0 commit comments