Deploy purely static pages to SWA without creating a `public` subfolder about static-web-apps-cli HOT 2 OPEN

I ran into something similar you mention recently. However, the swa deploy command is supposed to work against the output from the swa build command.

The trick with purely static site is to make use of script commands in a package.json to copy your source to a directory that you can pass into the swa deploy command.

You'll need the following files (tweak commands/paths as necessary)

package.json

{
  "scripts": {
    "build": "robocopy src src\\dist /XD *dist* /s /purge > nul & if ErrorLevel 8 (exit /B 1) else (exit /B 0)"
  }
}

The above command will copy all source files from the src directory to src\dist, including sub directories but excluding the dist folder. It will also remove files in the dist that do not exist in the source. The additional command translates the non zero success exit code from robocopy to a zero exit code, otherwise it will fail.

swa-cli.config.json

{
  "$schema": "https://aka.ms/azure/static-web-apps-cli/schema",
  "configurations": {
    "app": {
      "appLocation": "src",
      "outputLocation": "dist",
      "appBuildCommand" : "npm run build"
    }
  }
}

Your project directory structure should look like this:

\
¬\src
¬\src\index.html
¬\src\staticwebapp.config.json
¬\src\any-other-files-or-directories
¬\src\dist
package.json
swa-cli.config.json

Then simply run the following command from your root directory (the one above \src):

swa build && swa deploy [options]

from static-web-apps-cli.

I'm just hoping a better DX for the SWA newbies especially for the pure front-end devs. They might not know anything about Node.js or any backend stuff.

from static-web-apps-cli.