oriservice-windows-arm64 - npm Package Compare versions

Comparing version 0.0.0-pre-alpha.2-a56aa5f to 0.0.0-pre-alpha.2-a573d66

package.json

 {
   "name": "oriservice-windows-arm64",
   "license": "MIT",
-  "version": "0.0.0-pre-alpha.2-a56aa5f",
+  "version": "0.0.0-pre-alpha.2-a573d66",
   "repository": {
@@ -6,0 +6,0 @@ "url": "https://github.com/microsoft/ori"

README.md

@@ -98,3 +98,3 @@ # ori
 
-Rather than alwasy running a single esbuild build, it is sometimes more performant
+Rather than always running a single esbuild build, it is sometimes more performant
 or practical to run multiple separate builds. The different ways of coordinating and
@@ -111,3 +111,3 @@ connecting these separate builds are called "build strategies".
 This build strategy scans your repository for information about external dependencies on startup,
-and uses that information to build all of your external dependenices as a separate build.
+and uses that information to build all of your external dependencies as a separate build.
 
@@ -206,15 +206,15 @@ This tends to speed up interactive iterative builds, because it cuts out the dependencies from
 
-# Build an entry named "OWA Mail" from the entrypoints map, with codesplitting
+# Build an entry named "OWA Mail" from the entry points map, with code-splitting
 # Note that this has to be loaded with a script type="module" entrypoint,
-# since esbuild codesplitting forces esm modules
+# since esbuild code-splitting forces esm modules
 go run . -config=../ori.json -entry="OWA Mail" -split
 
-# Generate a cpu profile for initial and incrmental builds (the traces directory must already exist)
+# Generate a cpu profile for initial and incremental builds (the traces directory must already exist)
 go run . -config=../ori.json -entry="OWA Mail" -traceInitialBuild -traceIncrementalBuilds -cpuprofile=traces/cpu.pprof
 
-# Analyse cpu profiles (constains overview of CPU time)
+# Analyze cpu profiles (contains overview of CPU time)
 go tool pprof -http=localhost:8080 traces/cpu.pprof.initial*
 go tool pprof -http=localhost:8080 traces/cpu.pprof.incremental*
 
-# Analyse traces
+# Analyze traces
 go tool trace traces/trace.out.*
@@ -244,3 +244,3 @@
 
-  For now, `ori` will remain extremly opinionared on what the monorepo shape must look like. As much as possible, we want to prefer convention over configuration.
+  For now, `ori` will remain extremely opinionated on what the monorepo shape must look like. As much as possible, we want to prefer convention over configuration.
 
@@ -247,0 +247,0 @@ In the same vein, rather than implementing plugins or encouraging people to fork and make their own custom builds of `ori`, new functionality will be added to the same `ori` binaries as needed.

No alert changes

Improved metrics

Total package byte prevSize

222996

increased by247.83%

No dependency changes