Merge Modular 4 Changes to Main

.changeset/blue-turtles-shake.md

@@ -0,0 +1,5 @@
+---
+'modular-scripts': major
+---
+
+Removed commands: convert, init, port, rename

.changeset/cyan-flowers-rest.md

@@ -0,0 +1,6 @@
+---
+'modular-scripts': major
+---
+
+Changed default CDN from Skypack to esm.sh as skypack is no longer actively
+maintained. Add support for configuring modular through a configuration file.

.changeset/fair-kangaroos-retire.md

@@ -0,0 +1,5 @@
+---
+'modular-scripts': patch
+---
+
+Test pattern now includes jsx

.changeset/fluffy-dragons-behave.md

@@ -0,0 +1,14 @@
+---
+'create-modular-react-app': major
+'eslint-config-modular-app': major
+'modular-scripts': major
+'modular-template-app': patch
+'modular-template-esm-view': patch
+'modular-template-view': patch
+---
+
+Added Node 18 engine support
+Upgraded Jest from 26 to 29 as 26 wasn't compatible with Node 18
+Upgraded to rollup-plugin-esbuild 5, dropping support for Node 14.17 and below
+Supported Node versions now: ^14.18.0 || >=16.10.0 || >=18.0.0
+Changed Jest flag --watchAll default to false (was previously true if running locally and not in CI)

.changeset/green-shrimps-build.md

@@ -0,0 +1,5 @@
+---
+"modular-scripts": major
+---
+
+Fully selective `modular test` command interface, compatible with `modular build`.

.changeset/itchy-dancers-brush.md

@@ -0,0 +1,6 @@
+---
+'eslint-config-modular-app': major
+'modular-scripts': major
+---
+
+Updated eslint to ^8.0.0 and minimum supported TypeScript version to 4.5.3

.changeset/light-countries-report.md

@@ -0,0 +1,5 @@
+---
+'create-modular-react-app': major
+---
+
+Bumped default TypeScript version to ^4.8.3

.changeset/odd-bees-speak.md

@@ -0,0 +1,12 @@
+---
+"create-modular-react-app": minor
+"modular-scripts": minor
+"modular-template-app": minor
+"modular-template-esm-view": minor
+"modular-template-package": minor
+"modular-template-source": minor
+"modular-template-view": minor
+---
+
+Generate README inside newly created packages
+Improve root and default workspaces container README

.changeset/purple-numbers-camp.md

@@ -0,0 +1,5 @@
+---
+'modular-scripts': minor
+---
+
+App type modular packages are no longer required to be private

.changeset/wet-gifts-count.md

@@ -0,0 +1,5 @@
+---
+'modular-scripts': major
+---
+
+Sunset modular-site package

.github/workflows/release.yml

@@ -20,7 +20,7 @@ jobs:
       - name: Use Node.js
         uses: actions/setup-node@v3.3.0
         with:
-          node-version: '14.17.0'
+          node-version: '14.18.0'
           registry-url: https://registry.npmjs.org/
           cache: 'yarn'
 

.github/workflows/static.yml

@@ -29,7 +29,7 @@ jobs:
       - name: Use Node.js
         uses: actions/setup-node@v3.3.0
         with:
-          node-version: '14.17.0'
+          node-version: '14.18.0'
           cache: 'yarn'
 
       - name: 'Install Dependencies'

.github/workflows/test-windows.yml

@@ -20,7 +20,7 @@ jobs:
       fail-fast: false
       matrix:
         os: [windows-latest]
-        node-version: ['14.17.0', '16.x']
+        node-version: ['14.18.0', '16.x', '18.x']
 
     steps:
       - uses: actions/checkout@v3
@@ -34,4 +34,6 @@ jobs:
       - name: 'Build internal prerequisites'
         run: yarn workspace @modular-scripts/workspace-resolver build
       - name: Run Windows tests
-        run: yarn test esmView.test.ts workspace-resolver addPackage.test.ts
+        run:
+          yarn test --regex esmView.test.ts workspace-resolver
+          addPackage.test.ts

.github/workflows/test.yml

@@ -22,7 +22,7 @@ jobs:
       fail-fast: false
       matrix:
         os: [ubuntu-latest]
-        node-version: ['14.17.0', '16.x']
+        node-version: ['14.18.0', '16.x', '18.x']
 
     steps:
       - uses: actions/checkout@v3

.gitignore

@@ -53,3 +53,9 @@ yarn-error.log*
 .tsbuildinfo
 *.tsbuildinfo
 
+# Local Jekyll preview of docs
+docs/_site
+docs/.bundle
+docs/vendor
+docs/Gemfile*
+

__fixtures__/templates/modular-template-app/README.md

@@ -0,0 +1 @@
+# This is a README placeholder for this template fixture

__fixtures__/templates/modular-template-filter/README.md

@@ -0,0 +1 @@
+# This is a README placeholder for this template fixture

__fixtures__/templates/modular-template-no-filter/README.md

@@ -0,0 +1 @@
+# This is a README placeholder for this template fixture

__fixtures__/test-config/.modular.js

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

docs/commands/add.md

@@ -3,48 +3,79 @@ parent: Commands
 title: modular add
 ---
 
-# `modular add <packageName>`
+# `modular add [options] [packageName]`
 
-Adds a new package by creating a new workspace at `packages/<packageName>`,
-omitting the scope if the package is
+Adds a new package by creating a new package at the workspace located at
+`packages/<packageName>`, omitting the scope if the package is
 [scoped](https://docs.npmjs.com/cli/v8/using-npm/scope). If `--path <somePath>`
-is specified, create the workspace at `<somePath>/<packageName>`.
+is specified, the command creates the workspace at `<somePath>/<packageName>`.
 
 (i.e. `modular add my-app` would create a package in `packages/my-app`,
 `modular add @scoped/my-scoped-app` would create a package in
 `packages/my-scoped-app` and `modular add lib-a --path libs` would create a
 package in `libs/lib-a`)
 
-Packages can currently be one of the following types:
+The `modular add` command prompts the user to choose the Modular `type` of the
+package it's about to create. The next section briefly describes the various
+types that can be created by the `modular add` command. For an in-depth
+discussion of the available package types and their characteristics, please see
+[this page](../package-types/index.md).
 
-- A standalone `app`. This corresponds to a static Single Page Application (SPA)
-  project in a workspace. Inside this workspace, you can import packages from
-  other workspaces freely, and features like jsx and typechecking work out of
-  the box.
+### Standalone (bundled) package types
 
-- An `esm-view`, which is a package that typically exports a React component by
-  default. ESM Views are built as ES modules that can be `import`ed at runtime
-  by a host to implement a [micro frontend](../concepts/microfrontends.md)
-  architecture or started as a normal standalone application. See also
-  [the view building reference](../esm-views/index.md)
+These package types are built with [Webpack v5](https://webpack.js.org/) or, if
+specified in the [configuration](../configuration.md),
+[esbuild](https://esbuild.github.io/). Modules imported in the source of these
+package types are bundled in the final result (in case of `esm-view`s, only
+local modules get bundled, and external dependencies are rewritten to use an
+external ESM CDN. [This section](../esm-views/index.md) explains the process in
+more depth).
 
-- A `view`, which is a `package` that exports a React component by default. Read
-  more about Views in [this explainer](../concepts/views.md).
+- [`app`](../package-types/app.md). This package type corresponds to a static
+  Single Page Application (SPA) project in a workspace. It's possible to specify
+  a custom `index.html` file and public assets in the `public` directory. See
+  [this page](../package-types/#app) for more information about apps.
 
-- A generic JavaScript `package`. You can use this to create a library with an
-  entry point that gets transpiled to Common JS and ES Module format when built.
-  Packages can be [built](../commands/build.md) but not
-  [start](../commands/start.md)ed by Modular.
+- [`esm-view`](../package-types/esm-view.md). This package type is an app that
+  gets built as an ES module that can be imported at runtime. `esm-view`s are
+  typically used to implement a [micro-frontend](../concepts/microfrontends.md)
+  architecture. `esm-views`, when [built](./build.md) or [started](./start.md)
+  will also generate a `index.html` file that tries to load the ES Module and
+  render its default export as a React component onto the DOM (standalone mode).
+  See also [the esm-view reference](../esm-views/index.md) for an in-depth
+  introduction.
 
-- A `source`, which is a shared package that is imported by other packages from
-  source (i.e. directly importing its source), and it's never built standalone
-  or published. This kind of package is never [built](../commands/build.md) or
-  [start](../commands/start.md)ed by Modular.
+### Library package types
+
+These package types are either built with
+[Rollup.js](https://rollupjs.org/guide/en/) as CommonJS and ES Modules or, in
+case of `source` modules, they are not built at all. Library package types get
+typically published to NPM (`package` and `view` types) or get imported by other
+packages in the monorepo (`source` type). For this reason, files are transpiled
+separately on build and external dependencies are never "pulled in" (i.e. not
+included in a bundle).
+
+- [`package`](../package-types/package.md). This is a generic package with a
+  single entry point. It's normally used to create a publishable library that
+  gets transpiled to CommonJS and ES Module format when built. Packages can be
+  [built](../commands/build.md) but not [start](../commands/start.md)ed by
+  Modular.
+
+- [`view`](../package-types/view.md). This is a `package` that exports a default
+  React component. Views are built exactly like `package`s, but, since Modular
+  knows that the default export can be rendered, `view`s can be
+  [`modular start`](../start.md)ed to preview them locally.
+
+- [`source`](../package-types/source.md). A shared package that is imported by
+  other package types in the monorepo, directly specifying one or more of its
+  source files. This kind of package can be never [built](../commands/build.md)
+  or [start](../commands/start.md)ed by Modular.
 
 ## Options:
 
-`--path`: Optionally set the directory in which the workspace is created. If the
-provided path is outside (i.e., not a descendant) of the paths specified in
+`--path <targetPath>`: Optionally set the directory in which the workspace is
+created. If the provided path is outside (i.e., not a descendant) of the paths
+specified in
 [the `workspaces` field](https://classic.yarnpkg.com/lang/en/docs/workspaces/#toc-how-to-use-it)
 of the root `package.json`, the command will fail
 
@@ -55,4 +86,4 @@ of the root `package.json`, the command will fail
 
 `--template <templateName>`: Use the package `templateName` from the repository
 or the registry as a template for the new package. Find more information about
-Modular templates [in this page](../concepts/templates.md)
+Modular templates [in this page](../package-types/template.md)

docs/commands/build.md

@@ -3,7 +3,7 @@ parent: Commands
 title: modular build
 ---
 
-# `modular build [packages...]`
+# `modular build [options] [packages...]`
 
 Search workspaces based on their `name` field in the `package.json` and build
 them according to their respective `modular.type`, in order of dependency (e.g.
@@ -13,6 +13,13 @@ The output directory for built artifacts is `dist/`, which has a flat structure
 of modular package names. Each built app/view/package is added to the `dist/` as
 its own folder.
 
+When `packages` is empty and no selective options have been specified (for
+example when running `yarn modular build`), all packages in the monorepo will be
+built. When `packages` contains one or more non-existing package name, the
+non-existing packages will be ignored without an error. If any package or
+selective option have been defined but the final set of regular expressions is
+empty, Modular will write a message to `stdout` and exit with code `0`.
+
 For views and packages, package names are transformed to `Param case` (e.g.
 this-is-param-case) in `dist/`
 
@@ -25,7 +32,7 @@ this-is-param-case) in `dist/`
 
 `--preserve-modules`: Preserve module structure in generated modules.
 
-`--changed`: Build only packages whose workspaces contain files that have
+`--changed`: Build only the packages whose workspaces contain files that have
 changed. Files that have changed are calculated comparing the current state of
 the repository with the branch specified by `compareBranch` or, if
 `compareBranch` is not set, with the default git branch.

docs/commands/check.md

@@ -3,11 +3,13 @@ parent: Commands
 title: modular check
 ---
 
-# `modular check`
+# `modular check [options]`
 
 Checks the modular root repo has yarn workspaces and modular packages are set up
 properly and checks your package tree for issues with your dependencies.
 
 ## Options:
 
-`--fix`: Run autofix over applications.
+`--fix`: Run autofix over applications
+
+`--verbose`: Run yarn commands with the --verbose flag set

docs/commands/lint.md

@@ -3,7 +3,7 @@ parent: Commands
 title: modular lint
 ---
 
-# `modular lint`
+# `modular lint [options] [regexes...]`
 
 `modular lint` will check the diff between the current branch and your remote
 origin default branch (i.e. `master` or `main`) and only lint the `.ts`, `.tsx`,