This folder contains the human-readable source for this plugin's built/compiled JavaScript assets, per the WordPress.org Plugin Directory guideline requiring public access to the unminified source of any built code:

- webcomponent/main.js
  Source for js/swifflegrid.js (the <swiffle-grid> web component used on both the front end and in the block/widget editors).

- swiffle/
  Source for build/swiffle/index.js (the Gutenberg block's editor script). Mirrors src/swiffle/ in this repository, with comments stripped.

These files are regenerated automatically as part of this plugin's build process and are kept in sync with every release — they are not meant to be edited directly.

Note: sources originally authored as .jsx / .scss are published here with .js / .css extensions; content is unchanged.

Build tools used
-----------------
- swiffle/ (Gutenberg block, build/swiffle/index.js)
  Built with Parcel (https://parceljs.org/), using React JSX (@babel/preset-react)
  and Sass for styles. Build command, run from the plugin's own repository root
  (not from this distributed copy, which does not include package.json/
  node_modules): `parcel build src/swiffle/index.js --no-optimize
  --no-scope-hoist --no-cache --dist-dir build/swiffle`.

- webcomponent/main.js (js/swifflegrid.js)
  Built with Webpack + Babel, from a separate internal project that holds
  the <swiffle-grid> web component. The file is a single, self-contained
  entry point — it declares no imports and depends on no other modules —
  so no project-specific Webpack config is needed to reproduce the build.
  Webpack's own single-entry defaults apply directly:
  `webpack published-source/webcomponent/main.js -o dist --output-filename
  swifflegrid.js --mode production`, with Babel's `@babel/preset-env`
  (default browser targets) run via `babel-loader` for the same
  older-browser transpilation and MIT-licensed runtime helpers documented
  in js/swifflegrid.js.LICENSE.txt. The file registers itself as a custom
  element (`customElements.define('swiffle-grid', ...)`) as its only
  side effect on load, so no separate bootstrap/wiring code is needed
  beyond loading the built file itself.

Both are ordinary JS bundlers — a JS/React developer already familiar with
Parcel or Webpack can set up an equivalent build targeting the source above
without needing this plugin's own internal build scripts.
