Update docs for new repository changes

Author: NotNite

src/content/docs/dev/helper-scripts.md

@@ -5,7 +5,7 @@ sidebar:
   order: 5
 ---
 
-[The mappings repository](https://github.com/moonlight-mod/mappings) contains a collection of known Webpack modules with human-readable names. It finds Webpack modules and creates an alias to them, as well as remapping exports.
+[The mappings package](https://github.com/moonlight-mod/moonlight/tree/main/packages/mappings) contains a collection of known Webpack modules with human-readable names. It finds Webpack modules and creates an alias to them, as well as remapping exports.
 
 ## Remapping in your own extension
 
@@ -56,18 +56,11 @@ export default Exports;
 
 When adding a new module:
 
-- `node generate.js imports --write` to write the new `src/modules.ts`
-
-When adding types to a module:
-
-- Add its path and a name to `generate.js`
+- If the module has types, add its path and a name to `generate.js`
   - Name should be the last part of the path except in cases where it breaks syntax (e.g. `highlight.js` -> `HighlightJS`)
   - Mappings for CSS class names should replace `.css` with `CSS`
-- `node generate.js types --write` to generate the new type index
-- `node generate.js declares "@moonlight-mod/wp/" > ../moonlight/packages/types/src/mappings.d.ts` to update import statements in moonlight
-  - You don't have to do this unless you're a moonlight core developer
-
-Remember to format with Prettier!
+- In `packages/mappings`, run `node generate.js`
+- Format with Prettier
 
 ## Finding names
 

src/content/docs/dev/mappings.md

@@ -14,11 +14,9 @@ Each package contains a `package.json` and a `tsconfig.json`. Most packages will
 
 ## Build system
 
-moonlight uses [esbuild](https://esbuild.github.io) as its build system. The build script (`build.mjs`) is a single file which handles building [each stage](#load-stages) of moonlight, as well as each [core extension](#core-extensions).
+moonlight uses [esbuild](https://esbuild.github.io) as its build system. The build script (`build.mjs`) is a single file which handles building [each stage](#load-stages) of moonlight, as well as each [core extension](#core-extensions). This build script shares code with custom extensions in [esbuild-config](https://github.com/moonlight-mod/moonlight/tree/main/packages/esbuild-config), so flaws like [needing dev server restarts](/ext-dev/pitfalls#restarting-dev-mode-is-required-in-some-scenarios) apply to moonlight itself as well.
 
-This build script is separate to [our esbuild-config repository](https://github.com/moonlight-mod/esbuild-config), which is used by third-party developers in their own extensions. A future goal is to use the esbuild-config repository in moonlight itself ([see open issue](https://github.com/moonlight-mod/moonlight/issues/222)). Even though they do not share code, the implementation is similar, so flaws like [needing dev server restarts](/ext-dev/pitfalls#restarting-dev-mode-is-required-in-some-scenarios) apply to moonlight itself as well.
-
-esbuild's plugin API is very simple, and as such, moonlight's build script contains [a lot of hacks to get desired behavior](https://github.com/moonlight-mod/moonlight/blob/c01adbed21f7d7963f1ccb3038c8550fcd6343f0/build.mjs#L170-L175). In the future, moonlight and the [extension template](https://github.com/moonlight-mod/create-extension) may switch to another build system, but there are no plans to switch from esbuild at this time.
+In the future, moonlight and the [extension template](https://github.com/moonlight-mod/create-extension) may switch to another build system, but there are no plans to switch from esbuild at this time.
 
 ## Core
 
@@ -138,11 +136,4 @@ After processing the extensions, it calls the `window._moonlightWebLoad` functio
 
 ## Other dependencies
 
-moonlight uses some other packages that are not in the workspace, like [LunAST](https://github.com/moonlight-mod/lunast), [moonmap](https://github.com/moonlight-mod/moonmap), and [mappings](https://github.com/moonlight-mod/mappings). These packages do *not* use esbuild, and instead use [tsc](https://www.typescriptlang.org/docs/handbook/compiler-options.html), because they do not need any special config and are published on npm.
-
-Sometimes, you may need to modify one of these libraries, and test them in a local copy of moonlight. This is a known pain point of working with moonlight, and there are several ways to accomplish this:
-
-- Use [pnpm link](https://pnpm.io/cli/link) or [the link script](/dev/helper-scripts#linkmjs). Several developers have reported weird desyncs after linking packages, so exercise caution when using these.
-- Edit the `package.json` of the desired package(s) to use the `file:` protocol.
-
-Remember to undo your changes when you're done linking the other library, and make sure that `pnpm-lock.yaml` hasn't been changed by your testing.
+moonlight uses some other packages that are not in the workspace, like [LunAST](https://github.com/moonlight-mod/lunast) and [moonmap](https://github.com/moonlight-mod/moonmap). Additionally, some packages in the moonlight monorepo must be published to npm, like [mappings](https://github.com/moonlight-mod/moonlight/tree/main/packages/mappings) and [esbuild-config](https://github.com/moonlight-mod/moonlight/tree/main/packages/esbuild-config). These packages do *not* use esbuild, and instead use [tsc](https://www.typescriptlang.org/docs/handbook/compiler-options.html).

src/content/docs/dev/project-structure.md

@@ -9,54 +9,38 @@ This page is mainly here for moonlight core developers who forget what they're d
 :::
 
 :::caution
-Version bumps are not done until a publish is required. Make sure to version bump moonlight (and types, if necessary) before publishing.
-
-When publishing to npm, versions are constant. Exercise caution.
+Version bumps are not done until a publish is required. When publishing to npm, versions are constant. Exercise caution.
 :::
 
 ## Publishing moonlight
 
-moonlight CI builds the `develop` branch automatically. This section is for publishing a new stable, versioned release.
+moonlight CI builds the `main` branch automatically. This section is for publishing a new stable, versioned release.
 
-- Checkout the `develop` branch.
-- Pull to ensure you have the latest changes.
 - Checkout the `main` branch.
-- Merge `develop` into `main`.
-- Update the version in the following files:
-  - `package.json`
-  - `packages/browser/manifest.json`
-  - `packages/browser/manifestv2.json`
-- Write `CHANGELOG.md`.
-  - Do not append to the changelog - remake it.
-- If any types changes were made in this release, [update the types version](#publishing-types).
+- Pull to ensure you have the latest changes.
+- Run `node scripts/version.mjs` to update the project version.
+  - If there were no changes to types or mappings, you can technically undo the version bump, though it's suggested to just leave it there out of caution. If there were any changes to mappings, types must always be updated to sync alongside it.
+- Write `CHANGELOG.md`. Do not append to the changelog - remake it.
 - Commit and push to `main`.
-  - Make sure to push before creating the tag, or you might confuse CI (reasons unknown).
-- Create a tag with the version, **starting with the character `v`**: `git tag vX.Y.Z`
+  - Make sure to push before creating the tag, or you might confuse CI.
+- Create a tag with the new version, **starting with the character `v`**: `git tag vX.Y.Z`
   - This `v` is very important. CI will not pick it up otherwise. The installers will not know what to do without it.
+  - Double triple check that you didn't mistype the version number (this has happened before).
 - Push the tag: `git push --tags`
-- Checkout the `develop` branch.
-- Merge `main` into `develop`.
-- Push to `develop`.
-
-## Publishing types
 
-- Update the version in `packages/types/package.json`.
-  - We originally didn't have the types version in sync with moonlight, but we're aiming to resync. Bump the patch version until we can eventually re-synchronize them.
-- Continue to publish a moonlight release like normal, and wait for CI to finish.
-- [Run the types workflow](https://github.com/moonlight-mod/moonlight/actions/workflows/types.yml) to manually trigger a release to npm.
-- If the manifest type was updated, regenerate the schema: `pnpx ts-json-schema-generator --path './packages/types/src/*.ts' --type ExtensionManifest -f ./tsconfig.json > ../moonlight-mod.github.io/public/manifest.schema.json`
+Packages will be published to npm alongside the GitHub release. If the extension manifest type was updated, regenerate the JSON Schema: `pnpx ts-json-schema-generator --path './packages/types/src/*.ts' --type ExtensionManifest -f ./tsconfig.json > ../moonlight-mod.github.io/public/manifest.schema.json`
 
 ## Publishing other libraries
 
-(e.g. moonmap, LunAST, mappings, create-extension)
+(e.g. moonmap, LunAST, create-extension)
 
 - Update package.json with a new version.
 - Commit and push to `main`.
 - Create a tag with the version, **starting with the character `v`**: `git tag vX.Y.Z`
   - Same reasoning as [above](#publishing-moonlight).
 - Push the tag: `git push --tags`
 - Wait for the package to be uploaded to npm.
-- Use [the update helper script](/dev/helper-scripts) to update the dependencies in moonlight if needed.
+- Update the dependencies in moonlight.
 
 ## Publishing the installer
 

src/content/docs/dev/publishing.md

@@ -18,7 +18,5 @@ For more information on project structure, [see the dedicated page](/dev/project
 
 - Ensure your commits pass Prettier/ESLint. This is a requirement for merge.
   - moonlight uses [husky](https://typicode.github.io/husky) to check lints on commit. This should have automatically been setup for you when running `pnpm install`.
-- Please make PRs to the `develop` branch instead of `main`.
-  - `develop` is merged into `main` when moonlight updates happen. Our in-progress work resides on `develop`.
 - Don't break the existing API surface.
   - Library extensions and moonlight globals cannot change in a way that breaks existing extensions (unless there is an upcoming API bump).

src/content/docs/dev/setup.md

@@ -5,13 +5,13 @@ sidebar:
   order: 8
 ---
 
-moonlight comes with [mappings](https://github.com/moonlight-mod/mappings) that automatically rename Discord's Webpack modules for you. You can import and use these modules in your extensions.
+moonlight comes with [mappings](https://github.com/moonlight-mod/moonlight/tree/main/packages/mappings) that automatically rename Discord's Webpack modules for you. You can import and use these modules in your extensions.
 
 mappings automatically detects unknown modules and remaps them to have consistent module IDs and export names.
 
 ## Browsing mappings
 
-There is no search system for mappings yet, but you can browse [the source repository](https://github.com/moonlight-mod/mappings) instead. Press `/` on your keyboard to search in the GitHub web UI.
+There is no search system for mappings yet, but you can browse [the source repository](https://github.com/moonlight-mod/moonlight/tree/main/packages/mappings) instead. Press `/` on your keyboard to search in the GitHub web UI.
 
 ## Notable modules