internal: Fix typos. (#1665)

* Fix typos

* Run prettier

* Add version file

.yarn/versions/186654ce.yml

@@ -0,0 +1,16 @@
+releases:
+  "@moonrepo/cli": patch
+  "@moonrepo/core-linux-arm64-gnu": patch
+  "@moonrepo/core-linux-arm64-musl": patch
+  "@moonrepo/core-linux-x64-gnu": patch
+  "@moonrepo/core-linux-x64-musl": patch
+  "@moonrepo/core-macos-arm64": patch
+  "@moonrepo/core-macos-x64": patch
+  "@moonrepo/core-windows-x64-msvc": patch
+  "@moonrepo/types": patch
+  website: patch
+
+declined:
+  - "@moonrepo/nx-compat"
+  - "@moonrepo/report"
+  - "@moonrepo/runtime"

CHANGELOG.md

@@ -189,7 +189,7 @@ may also have to unquarantine moon on your system. And lastly, we also suggest
 - Fixed an issue where a persistent task may not run or error with a missing dependency hash, if ran
   alongside many other persistent tasks.
 - Fixed an issue where "build" dependencies were being synced as project references.
-- Fixed an issue where the install depenencies action wouldn't run if the vendor directory
+- Fixed an issue where the install dependencies action wouldn't run if the vendor directory
   (node_modules) was missing, but our operation was previously cached.
 - Fixed an issue where token variables were not being replaced in task scripts.
 

CHANGELOG_V0.md

@@ -285,7 +285,7 @@ immediately see the benefits in your CI pipelines.
 
 - Fixed an issue where directories in task `inputs` not using `**/*` would crash git.
 - Fixed an issue where the project graph cache was not always resetting based on changes.
-- Fixed an issue where run report action durations were innacurate.
+- Fixed an issue where run report action durations were inaccurate.
 
 #### ⚙️ Internal
 

crates/action-graph/src/action_graph.rs

@@ -23,7 +23,7 @@ impl ActionGraph {
         ActionGraph { graph }
     }
 
-    pub fn creater_iter(&self, indices: Vec<NodeIndex>) -> ActionGraphIter {
+    pub fn create_iter(&self, indices: Vec<NodeIndex>) -> ActionGraphIter {
         ActionGraphIter::new(&self.graph, indices)
     }
 

crates/action-graph/src/action_graph_builder.rs

@@ -530,12 +530,12 @@ impl<'app> ActionGraphBuilder<'app> {
             self.initial_targets.insert(target.clone());
 
             // Run the target
-            let (inserted_targets, inserted_indicies) = self.run_task_by_target(target, &reqs)?;
+            let (inserted_targets, inserted_indices) = self.run_task_by_target(target, &reqs)?;
 
             // Track the primary targets
             self.primary_targets.extend(inserted_targets);
 
-            inserted_nodes.extend(inserted_indicies);
+            inserted_nodes.extend(inserted_indices);
         }
 
         Ok(inserted_nodes)

crates/action-graph/tests/action_graph_test.rs

@@ -56,7 +56,7 @@ fn create_rust_runtime() -> Runtime {
 
 fn topo(graph: ActionGraph) -> Vec<ActionNode> {
     let mut nodes = vec![];
-    let mut iter = graph.creater_iter(graph.sort_topological().unwrap());
+    let mut iter = graph.create_iter(graph.sort_topological().unwrap());
 
     while iter.has_pending() {
         if let Some(index) = iter.next() {

crates/codegen/src/codegen.rs

@@ -69,7 +69,7 @@ impl<'app> CodeGenerator<'app> {
                     Template::new(Id::clean(fs::file_name(&template_root))?, template_root)?;
 
                 if let Some(existing_template) = self.templates.get(&template.id) {
-                    return Err(CodegenError::DulicateTemplate {
+                    return Err(CodegenError::DuplicateTemplate {
                         id: template.id,
                         original: existing_template.root.clone(),
                         current: template.root,

crates/codegen/src/codegen_error.rs

@@ -41,7 +41,7 @@ pub enum CodegenError {
         .original.style(Style::Path),
         .current.style(Style::Path),
     )]
-    DulicateTemplate {
+    DuplicateTemplate {
         id: Id,
         original: PathBuf,
         current: PathBuf,

crates/config/src/project/dep_config.rs

@@ -37,7 +37,7 @@ cacheable!(
         /// Scope of the dependency relationship.
         pub scope: DependencyScope,
 
-        /// Source of where the dependeny came from.
+        /// Source of where the dependency came from.
         pub source: DependencySource,
 
         /// Metadata about the source.

crates/config/src/project_config.rs

@@ -147,7 +147,7 @@ cacheable!(
         /// The technology stack of the project, for categorizing.
         pub stack: StackType,
 
-        /// A list of tags that this project blongs to, for categorizing,
+        /// A list of tags that this project belongs to, for categorizing,
         /// boundary enforcement, and task inheritance.
         pub tags: Vec<Id>,
 

crates/project-builder/src/project_builder.rs

@@ -261,7 +261,7 @@ impl<'app> ProjectBuilder<'app> {
             }
         }
 
-        // Tasks can depend on arbitray projects, so include them also
+        // Tasks can depend on arbitrary projects, so include them also
         for task_config in tasks.values() {
             for task_dep in &task_config.deps {
                 if let TargetScope::Project(dep_id) = &task_dep.target.scope {

crates/task-runner/src/command_executor.rs

@@ -78,7 +78,7 @@ impl<'task> CommandExecutor<'task> {
         // Prepare state for the executor, and each attempt
         let mut run_state = TargetState::Failed;
 
-        self.prepate_state(context, report_item);
+        self.prepare_state(context, report_item);
 
         // For long-running process, log a message on an interval to indicate it's still running
         self.start_monitoring();
@@ -228,7 +228,7 @@ impl<'task> CommandExecutor<'task> {
         }
     }
 
-    fn prepate_state(&mut self, context: &ActionContext, report_item: &mut TaskReportItem) {
+    fn prepare_state(&mut self, context: &ActionContext, report_item: &mut TaskReportItem) {
         let is_primary = context.is_primary_target(&self.task.target);
         let mut output_prefix = None;
 

legacy/node/lang/src/pnpm/dependency_path.rs

@@ -181,7 +181,7 @@ mod tests {
     }
 
     #[test]
-    fn parses_from_custom_regsitry_with_peer_deps() {
+    fn parses_from_custom_registry_with_peer_deps() {
         assert_eq!(
             PnpmDependencyPath::parse("example.com/foo/[email protected]"),
             PnpmDependencyPath {

packages/types/src/project-config.ts

@@ -26,7 +26,7 @@ export interface DependencyConfig {
 	 */
 	scope: DependencyScope;
 	/**
-	 * Source of where the dependeny came from.
+	 * Source of where the dependency came from.
 	 *
 	 * @default 'explicit'
 	 * @type {'explicit' | 'implicit'}
@@ -255,7 +255,7 @@ export interface ProjectConfig {
 	 */
 	stack: StackType;
 	/**
-	 * A list of tags that this project blongs to, for categorizing,
+	 * A list of tags that this project belongs to, for categorizing,
 	 * boundary enforcement, and task inheritance.
 	 */
 	tags: string[];
@@ -285,7 +285,7 @@ export interface PartialDependencyConfig {
 	 */
 	scope?: DependencyScope | null;
 	/**
-	 * Source of where the dependeny came from.
+	 * Source of where the dependency came from.
 	 *
 	 * @default 'explicit'
 	 */
@@ -484,7 +484,7 @@ export interface PartialProjectConfig {
 	 */
 	stack?: StackType | null;
 	/**
-	 * A list of tags that this project blongs to, for categorizing,
+	 * A list of tags that this project belongs to, for categorizing,
 	 * boundary enforcement, and task inheritance.
 	 */
 	tags?: string[] | null;

website/blog/2022-09-01_v0.13.mdx

@@ -6,7 +6,7 @@ tags: [hasher, toolchain]
 ---
 
 With this release, we've landed some improvements to our smart hashing, and paved the road for
-additional languagues and tooling.
+additional languages and tooling.
 
 <!--truncate-->
 

website/blog/2023-01-04_2023-roadmap.mdx

@@ -29,7 +29,7 @@ community and our long-term vision, with some such features as:
 - Code generation / scaffolding
 - Dockerfile integration
 - Remote caching
-- New langauage agnostic toolchain
+- New language agnostic toolchain
 - Onboarding of 5 new languages: Rust, Go, PHP, Python, Ruby
 - Rewritten project and dependency graphs
 - Project-level toolchain overrides
@@ -111,12 +111,12 @@ However, that's not the entirety of the frontend ecosystem, as [Deno](https://de
 [Bun](https://bun.sh/) have been gaining traction this past year, and of course, moon will support
 both of them as first-class platforms by end of year.
 
-Futhermore, we recently landed tier 1 support for 5 new languages: Rust, Ruby, PHP, Python, and Go.
+Furthermore, we recently landed tier 1 support for 5 new languages: Rust, Ruby, PHP, Python, and Go.
 Our end of year goal for these languages is to provide full tier 2 support. Tier 3 support is still
 an unknown, as we need to investigate the best possible way to integrate these languages into the
 toolchain (this work is ongoing). We'll also add new languages based on demand.
 
-With all that being said, this is our tenative timeline around
+With all that being said, this is our tentative timeline around
 [language support](/docs#supported-languages) (which may shift at any time):
 
 - **Q1**

website/blog/2023-02-08_moonbase.mdx

@@ -28,7 +28,7 @@ improvements in CI times, upwards of 90%.
 ## What is moonbase?
 
 You may be asking yourself, what is moonbase? [moonbase](/moonbase) is a new cloud service that
-we've been working on to solve an array of problems in regards to repository and continous
+we've been working on to solve an array of problems in regards to repository and continuous
 integration health.
 
 <Image src={require('../static/img/home/org.png')} width="80%" />

website/blog/2023-02-13_v0.24.mdx

@@ -163,7 +163,7 @@ full list of changes.
   support.
 - Added a `hasher.walkStrategy` setting to `.moon/workspace.yml`.
 - Updated task `outputs` to support token functions (`@group`, `@globs`, etc).
-- Reworked our comparison/baseline estimations calcuations.
+- Reworked our comparison/baseline estimations calculations.
 
 ## What's next?
 

website/blog/2023-03-15_proto-v0.3.mdx

@@ -47,7 +47,7 @@ $ proto install go -- --no-gobin
 
 ## Better version requirement detection
 
-Previously when proto encounted a version requirement (`^`, `~`, `>=`, etc) during version
+Previously when proto encountered a version requirement (`^`, `~`, `>=`, etc) during version
 detection, we would attempt to resolve a version that satisfied the requirement based on versions
 available in the remote manifest (what's been officially released). While this worked, it would
 result in far too many local installs as that satisfied version constantly changed.

website/blog/2023-04-21_proto-v0.7.mdx

@@ -42,7 +42,7 @@ All 4 of these pieces can be solved with a configuration file, and as such, we o
 other benefits of a schema is that it's _easy to write, read, and maintain_, doesn't require any
 code, and doesn't force you into a specific programming language.
 
-To demonstate how this plugin works, here's an example of a [moon](/moon) TOML schema.
+To demonstrate how this plugin works, here's an example of a [moon](/moon) TOML schema.
 
 ```toml title="moon-schema.toml"
 name = "moon"

website/blog/2023-05-08_moon-v1.5.mdx

@@ -78,7 +78,7 @@ tasks:
     platform: 'rust'
 ```
 
-> We also attempt to detect this automatially by comparing command names and checking for the
+> We also attempt to detect this automatically by comparing command names and checking for the
 > existence of files like `Cargo.toml`.
 
 ## Updated `moon init` command

website/blog/2023-08-21_moon-v1.12.mdx

@@ -110,7 +110,7 @@ tasks:
       interactive: true
 ```
 
-## Tokens in enviroment variables
+## Tokens in environment variables
 
 Up until now, [token functions and variables](/docs/concepts/token) were only supported in task
 commands, args, inputs, and outputs, but not environment variables... why? Honestly, there was no

website/blog/2023-09-04_proto-v0.16.mdx

@@ -47,7 +47,7 @@ tool, its manifest, _all_ installed versions, and the entire `~/.proto/tools/<id
 $ proto clean --purge node
 ```
 
-Additionaly, a new `--purge-plugins` option can be used to delete all downloaded plugins (the
+Additionally, a new `--purge-plugins` option can be used to delete all downloaded plugins (the
 `~/.proto/plugins` directory). Useful for house keeping or if you want to start fresh.
 
 ```shell

website/blog/2023-12-19_proto-v0.26-rc.mdx

@@ -30,7 +30,7 @@ files were a bit better, but still not great.
 
 For the most part, executing a shim as-is and doing basic work was fine, but once you needed a
 complex scenario (like above), it broke down pretty quickly. It was also further exacerbated when
-dealing with nested shim exections, for example, `npm` calls `node` under the hood. The parent shim
+dealing with nested shim executions, for example, `npm` calls `node` under the hood. The parent shim
 may be executed with `.ps1` but the child may be `.cmd`, and these do not play well together.
 
 The other problem on Windows is that scripts are not true executables, and are not easily located on
@@ -43,7 +43,7 @@ We wrote our own Rust based executable, that will replace all of the custom shim
 properly handle all of the required scenarios. This new executable is named `proto-shim`
 (`proto-shim.exe` on Windows) and is published alongside the `proto` binary.
 
-This new executable solves all of the following problems (hopfully):
+This new executable solves all of the following problems (hopefully):
 
 - Locatable on `PATH` (is an `.exe` for Windows)
 - Can pipe/redirect data

website/blog/2023-12-21_proto-v0.26.mdx

@@ -27,7 +27,7 @@ exactly what we did. In this release, we wrote our own Rust based executable, th
 of the custom shim scripts. This new executable is named `proto-shim` (`proto-shim.exe` on Windows)
 and is published alongside the `proto` binary.
 
-This new executable solves all of the following problems (hopfully):
+This new executable solves all of the following problems (hopefully):
 
 - Locatable on `PATH` (is an `.exe` for Windows)
 - Can pipe/redirect data

website/blog/2024-02-26_moon-v1.22.mdx

@@ -93,7 +93,7 @@ features.
 :::info
 
 An awesome feature that didn't make it in time for this release, is an npm package for Nx
-compatiblity, that will allow Nx executors/plugins to be executed through moon, without the
+compatibility, that will allow Nx executors/plugins to be executed through moon, without the
 requirement of Nx itself. This will allow for a seamless transition from Nx to moon, without the
 need to change any of your existing Nx executors/plugins till later.
 

website/blog/2024-03-25_moon-v1.23.mdx

@@ -66,7 +66,7 @@ And lastly, we're introducing some additions and improvements to template
 
 Last month in [moon v1.22](./moon-v1.22), we introduced the [`stack`](/docs/config/project#stack)
 setting for organizing projects into what tech stack they belong to. This is primarily for
-organizational purposes, and improving our project constaints implementation.
+organizational purposes, and improving our project constraints implementation.
 
 Based on community feeedback, we've expanded the `stack` setting to also apply for
 [task inheritance](http://localhost:3000/docs/concepts/task-inheritance#scope-by-project-metadata).

website/blog/2024-07-26_proto-v0.39.mdx

@@ -17,7 +17,7 @@ as a means of bootstrapping your shell with necessary paths and variables. Since
 handful of bugs and focused on performance for this release.
 
 In this release, we've reduced the time it took to execute activation from 200-300ms down to
-10-20ms. We've also fixed some syntax isses around Bash and Zsh shells.
+10-20ms. We've also fixed some syntax issues around Bash and Zsh shells.
 
 ## Merged `proto install` and `proto use` commands
 

website/blog/2024-09-02_moon-v1.28.mdx

@@ -85,7 +85,7 @@ benefit, as it required consumers to open up config files to discover this metad
 write custom abstractions/tooling. We want to improve the integration of this information within
 moon, so to start, we're introducing a new token function [`@meta(key)`](/docs/concepts/token#meta).
 
-The [`@meta(key)`](/docs/concepts/token#meta) token function can be used to access project metdata
+The [`@meta(key)`](/docs/concepts/token#meta) token function can be used to access project metadata
 from both the [`project`](/docs/config/project#project) and
 [`project.metadata`](/docs/config/project#metadata-1) settings. The former values will be used
 as-is, while the latter values will be JSON stringified (since consumers can define anything).
@@ -137,8 +137,8 @@ tasks:
 
 Because `build` is disabled, its outputs may not be created. Additionally, if `build` is affected by
 touched files, the `analyze` task will not run automatically unless it was also affected. We try our
-best to accomdate these scenarios and "detect" when things should run or not, but it's fallible, as
-there's many ways that tasks can relate to each other.
+best to accommodate these scenarios and "detect" when things should run or not, but it's fallible,
+as there's many ways that tasks can relate to each other.
 
 To try and remedy this going forward, we're introducing the new `disallowRunInCiMismatch` experiment
 that will _hard error_ if an invalid relationship is configured. We want to try and capture how

website/docs/comparison.mdx

@@ -128,7 +128,7 @@ scripts being repeated constantly.
 right={
   <>
 
-moon avoids this overhead by using [task inheritance](#unique-features). No more repitition.
+moon avoids this overhead by using [task inheritance](#unique-features). No more repetition.
 
   </>
 }

website/docs/concepts/task.mdx

@@ -128,7 +128,7 @@ replace values. Refer to the table below for more differences between the 2.
 
 |                                          | Command                   | Script             |
 | :--------------------------------------- | :------------------------ | :----------------- |
-| Configued as                             | string, array             | string             |
+| Configured as                            | string, array             | string             |
 | Inheritance merging                      | ✅ via `mergeArgs` option | ⚠️ always replaces |
 | Additional args                          | ✅ via `args` setting     | ❌                 |
 | Passthrough args (from CLI)              | ✅                        | ❌                 |

website/docs/config/workspace.mdx

@@ -641,8 +641,8 @@ vcs:
 
 <HeadingApiLink to="/api/types/interface/VcsConfig#remoteCandidates" />
 
-(Git only) Defines a list of remote candidates to query agaist to determine merge bases. Defaults to
-"origin" and "upstream".
+(Git only) Defines a list of remote candidates to query against to determine merge bases. Defaults
+to "origin" and "upstream".
 
 ```yaml title=".moon/workspace.yml" {2-4}
 vcs:

website/docs/faq.mdx

@@ -230,7 +230,7 @@ hardest:
 
 - Run moon in a Docker container/image that has the correct environment and libs. For example, the
   `node:latest` image.
-- Upgrade the enviroment to a newer one. For example, Ubuntu 18 -> 22.
+- Upgrade the environment to a newer one. For example, Ubuntu 18 -> 22.
 - Try and install a newer libc
   ([more information](https://stackoverflow.com/questions/72513993/how-install-glibc-2-29-or-higher-in-ubuntu-18-04)).
 

website/docs/guides/extensions.mdx

@@ -103,7 +103,7 @@ likely be required! We suggest testing each converted task 1-by-1 to ensure it w
 The following features are not supported in moon, and are ignored when converting.
 
 - Most settings in `nx.json`.
-- Named input variants: externel dependencies, dependent task output files, dependent project
+- Named input variants: external dependencies, dependent task output files, dependent project
   inputs, or runtime commands.
 - Target `configurations` and `defaultConfiguration`. Another task will be created instead that uses
   `extends`.