docs: Add clean command.

src/Packemon.ts

@@ -25,7 +25,6 @@ import {
   PackemonPackageConfig,
   Platform,
   TypesBuild,
-  AnalyzeType,
 } from './types';
 
 const debug = createDebugger('packemon:core');
@@ -79,7 +78,7 @@ export default class Packemon {
     const options = optimal(baseOptions, {
       addEngines: bool(),
       addExports: bool(),
-      analyzeBundle: string('treemap').oneOf<AnalyzeType>(['sunburst', 'treemap', 'network']),
+      analyzeBundle: string().oneOf(['', 'sunburst', 'treemap', 'network']),
       checkLicenses: bool(),
       concurrency: number(1).gte(1),
       generateDeclaration: bool(),

src/commands/Clean.tsx

@@ -3,7 +3,7 @@ import Packemon from '../Packemon';
 
 export type CleanParams = [string];
 
-@Config('clean', 'Clean build artifacts from all packages.')
+@Config('clean', 'Clean build artifacts from packages.')
 export class CleanCommand extends Command<GlobalOptions, CleanParams> {
   @Arg.Params<CleanParams>({
     description: 'Project root that contains a `package.json`',

website/docs/build.md

@@ -1,14 +1,15 @@
 ---
 title: Building packages
+sidebar_label: build
 ---
 
 Packemon was primarily designed and engineered for building packages. But what is building you ask?
 Building is the process of parsing, transforming, and bundling a package's source code into
 distributable and consumable files for NPM, using community favorite tools like [Babel][babel] and
 [Rollup][rollup].
 
-With that being said, the `packemon build` command can be used to build all packages in a project
-according to their configured build targets (platform, formats, etc).
+With that being said, the `build` command can be used to build all packages in a project according
+to their configured build targets (platform, formats, etc).
 
 ```
 packemon build --checkLicenses --generateDeclaration
@@ -153,7 +154,7 @@ The environment preset is always enabled and configures the following.
 - `@babel/preset-env`
   - Defines `modules` and `targets` based on the chosen [platform](./config.md#platforms) and
     [format](./config.md#formats).
-  - Enables `spec` and disables `loose` for spec compliance.
+  - Enables `spec` (in development) and disables `loose` for closer compliance.
   - Enables `bugfixes` and `shippedProposals` for smaller file sizes.
   - Disables `useBuiltIns` as consumers of the package should polyfill accordingly.
 

website/docs/clean.md

@@ -0,0 +1,15 @@
+---
+title: Cleaning packages
+sidebar_label: clean
+---
+
+Building packages generate temporary files or folders that clutter a project. Sometimes these
+artifacts aren't properly cleaned up because a process failed midway. The `clean` command can be
+used to remove all temporary files _and_ all build artifacts (lib, esm, etc folders).
+
+```bash
+packemon clean
+```
+
+> Cleaning a project before a release is a good practice for ensuring unknown artifacts are not
+> distributed.

website/sidebars.js

@@ -6,7 +6,12 @@ module.exports = {
     'install',
     'setup',
     'config',
-    'build',
+    {
+      type: 'category',
+      label: 'Commands',
+      collapsed: false,
+      items: ['build', 'clean'],
+    },
     'advanced',
     {
       type: 'link',