chore: wip

Author: chrisbbreuer

.github/CONTRIBUTING.md

@@ -179,7 +179,7 @@ _By following these minor steps, Stacks is able to automatically release new ver
 
 When you're all done, head over to the [repository][stacks], and click the big green `Compare & Pull Request` button that should appear after you've pushed changes to your fork.
 
-Don't expect your PR to be accepted immediately or even accepted at all. Give the community time to vet it and see if it should be merged. Please don't be disheartened if it's not accepted. Your contribution is appreciated more than you can imagine, and even a unmerged PR can teach us a lot ❤️
+Don't expect your PR to be accepted immediately or even accepted at all. Give the community time to vet it and see if it should be merged. Please don't be disheartened if it’s not accepted. Your contribution is appreciated more than you can imagine, and even a unmerged PR can teach us a lot ❤️
 
 [typescript]: https://www.typescriptlang.org
 [vue]: https://vuejs.org/

bootstrap

@@ -14,7 +14,7 @@ if [ -n "$1" ]; then
       git clone https://github.com/stacksjs/stacks.git $1
       cd "$1" || exit 1
 
-      # Run the pkgx-install script (in case it's already installed, it will be updated to the latest version)
+      # Run the pkgx-install script (in case it’s already installed, it will be updated to the latest version)
       "./storage/framework/scripts/pkgx-install"
 
       echo "Project $1 has been created. Please open a new terminal, run 'bun run dev' to start the server."

docs/guide/composability.md

@@ -28,7 +28,7 @@ In concept, you can characterize a "composable library" as a collection of compo
 
 >Think of Lodash for "functions," and minimal HTML for the "components."
 
-## How do I know if it's right for me?
+## How do I know if it’s right for me?
 
 When wanting to adapt the "Composability-First Design" pattern, you will want to ask the following questions to identify whether or not this design pattern is a fit for you:
 

docs/guide/get-started.md

@@ -1,6 +1,6 @@
 # Get Started
 
-A core Stacks principle is to utilize sensible defaults. This means that it's incredibly easy to get started with this framework. However, Stacks is also very flexible and allows you to customize every aspect of it.
+A core Stacks principle is to utilize sensible defaults. This means that it’s incredibly easy to get started with this framework. However, Stacks is also very flexible and allows you to customize every aspect of it.
 
 This guide will help you get started with your first Stacks project. Simply run the following command in your terminal:
 

resources/components/README.md

@@ -23,7 +23,7 @@ Additionally, the `package.json` contains some useful snippets you likely want t
 
 ## 🤖 Usage
 
-Because this project is optimized toward the development of easily reusable & composable component libraries, it's very easy to use (and distribute):
+Because this project is optimized toward the development of easily reusable & composable component libraries, it’s very easy to use (and distribute):
 
 ```vue
 <script setup lang="ts">

storage/framework/core/actions/src/deploy/create-receipt-rule.ts

@@ -9,7 +9,7 @@ const s3 = new S3({ apiVersion: '2006-03-01' })
 
 // oddly, this somehow does not play well within a CDK construct
 // so we need to use the AWS SDK directly to create the rule
-// unsure whether it's an AWS or implementation issue
+// unsure whether it’s an AWS or implementation issue
 
 // need to query S3 to get the bucket name, based on whether the name contains -email-
 // which is indicative of the email bucket created by the CDK construct

storage/framework/core/actions/src/domains/add.ts

@@ -33,8 +33,8 @@ await updateNameservers(nameServers)
 
 const registrar: string = (await whois(domain, true)).parsedData.Registrar
 
-// usually for Route53 registered domains, we don't need to update create a hosted zone as it's already
-// done for us. But in case it's not, we still need to ensure it's created before we can deploy
+// usually for Route53 registered domains, we don't need to update create a hosted zone as it’s already
+// done for us. But in case it’s not, we still need to ensure it’s created before we can deploy
 if (registrar.includes('Amazon')) {
   if (options.deploy) {
     await runCommand('buddy deploy')

storage/framework/core/actions/src/generate/model-classes.ts

@@ -58,7 +58,7 @@ export class UserModel {
         if (prop in target)
           return target[prop]
 
-        // If it's a method on the UserModel, bind it
+        // If it’s a method on the UserModel, bind it
         const method = this[prop as keyof this]
         if (typeof method === 'function')
           return method.bind(this)

storage/framework/core/actions/src/upgrade.ts

@@ -21,7 +21,7 @@ export function checkForUncommittedChanges(options: UpgradeOptions) {
   catch (error: any) {
     if (error.status === 1) {
       // even though the ./stacks folder should not be edited, instead config values should be adjusted,
-      // there is a chance that users may apply local core edits, as it's totally acceptable, as long as
+      // there is a chance that users may apply local core edits, as it’s totally acceptable, as long as
       // the user knows what they are doing. There is also a change that simply the deps within stacks
       // folder have been updated and that could produce a diff.
       if (!options?.force) {

storage/framework/core/actions/src/upgrade/shell.ts

@@ -16,7 +16,7 @@ $.cwd(p.dirname(zshrcPath))
 let data = await $`cat ${p.basename(zshrcPath)}`.text()
 
 // Manipulate the data
-const pluginLineRegex = /^(?!#).*plugins=\(([^)]+)\)/m // ensure it's not a comment
+const pluginLineRegex = /^(?!#).*plugins=\(([^)]+)\)/m // ensure it’s not a comment
 const match = data.match(pluginLineRegex)
 
 if (match) {
@@ -27,10 +27,10 @@ if (match) {
     process.exit(ExitCode.FatalError)
   }
 
-  // 2. Add buddy to the list of plugins if it's not already there
+  // 2. Add buddy to the list of plugins if it’s not already there
   if (!plugins.includes('buddy')) {
     plugins.push('buddy')
-    // Trim each plugin name and ensure it's formatted correctly
+    // Trim each plugin name and ensure it’s formatted correctly
     const formattedPlugins = plugins.map(plugin => plugin.trim()).join('\n    ')
     const newPluginLine = `plugins=(\n    ${formattedPlugins}\n)`
     // Replace the old plugin line with the new one