Merge pull request #38 from NullVoxPopuli/prettier

Prettier

.prettierignore

@@ -0,0 +1,3 @@
+*.yaml
+*.yml
+*.md

.prettierrc.cjs

@@ -0,0 +1,3 @@
+module.exports = {
+  singleQuote: true,
+};

.vscode/settings.json

@@ -1,3 +1,3 @@
 {
   "editor.formatOnSave": true
-}
+}

README.md

@@ -39,10 +39,10 @@ Example Config:
 {
   plugins: [
     [
-      "decorator-transforms",
+      'decorator-transforms',
       {
         runtime: {
-          import: require.resolve("decorator-transforms/runtime"),
+          import: require.resolve('decorator-transforms/runtime'),
         },
       },
     ],
@@ -89,7 +89,7 @@ If you try to use the string name "decorator-transforms" in a babel config file,
 3. At the beginning of `app.js`, install the global runtime helpers:
 
    ```js
-   import "decorator-transforms/globals";
+   import 'decorator-transforms/globals';
    ```
 
    In classic builds, `"globals"` is the only `runtime` setting that works because ember-auto-import cannot see the output of this babel transform.

RELEASE.md

@@ -4,21 +4,21 @@ Releases in this repo are mostly automated using [release-plan](https://github.c
 
 ## Preparation
 
-Since the majority of the actual release process is automated, the remaining tasks before releasing are: 
+Since the majority of the actual release process is automated, the remaining tasks before releasing are:
 
--  correctly labeling **all** pull requests that have been merged since the last release
--  updating pull request titles so they make sense to our users
+- correctly labeling **all** pull requests that have been merged since the last release
+- updating pull request titles so they make sense to our users
 
 Some great information on why this is important can be found at [keepachangelog.com](https://keepachangelog.com/en/1.1.0/), but the overall
 guiding principle here is that changelogs are for humans, not machines.
 
 When reviewing merged PR's the labels to be used are:
 
-* breaking - Used when the PR is considered a breaking change.
-* enhancement - Used when the PR adds a new feature or enhancement.
-* bug - Used when the PR fixes a bug included in a previous release.
-* documentation - Used when the PR adds or updates documentation.
-* internal - Internal changes or things that don't fit in any other category.
+- breaking - Used when the PR is considered a breaking change.
+- enhancement - Used when the PR adds a new feature or enhancement.
+- bug - Used when the PR fixes a bug included in a previous release.
+- documentation - Used when the PR adds or updates documentation.
+- internal - Internal changes or things that don't fit in any other category.
 
 **Note:** `release-plan` requires that **all** PRs are labeled. If a PR doesn't fit in a category it's fine to label it as `internal`
 

package.json

@@ -31,7 +31,8 @@
   ],
   "scripts": {
     "build": "tsup --dts",
-    "lint": "tsc",
+    "lint": "tsc && prettier --check .",
+    "lint:fix": "prettier --write .",
     "start": "tsup --dts --watch",
     "test": "node --experimental-vm-modules node_modules/qunit/bin/qunit.js --require @swc-node/register tests/*-test.ts",
     "typecheck": "tsc",
@@ -46,12 +47,13 @@
     "@babel/plugin-proposal-decorators": "^7.23.3",
     "@babel/plugin-transform-class-properties": "^7.23.3",
     "@babel/plugin-transform-private-methods": "^7.23.3",
-    "@embroider/shared-internals": "^2.5.1",
     "@babel/preset-env": "^7.24.4",
+    "@embroider/shared-internals": "^2.5.1",
     "@swc-node/register": "^1.6.8",
     "@types/babel__core": "^7.20.4",
     "@types/node": "^20.9.1",
     "@types/qunit": "^2.19.8",
+    "prettier": "^3.3.3",
     "qunit": "^2.20.0",
     "release-plan": "^0.9.0",
     "tsup": "^7.3.0",

src/globals.ts

@@ -1,3 +1,3 @@
-import * as runtime from "./runtime.ts";
-import { globalId } from "./global-id.ts";
+import * as runtime from './runtime.ts';
+import { globalId } from './global-id.ts';
 (globalThis as any)[globalId] = runtime;