app-bundler 0.2.18 → 0.2.21

package/.circleci/config.yml

@@ -0,0 +1,37 @@
+# See: https://circleci.com/docs/2.0/configuration-reference
+version: 2.1
+
+orbs:
+  # See the orb documentation here: https://circleci.com/developer/orbs/orb/circleci/node
+  browser-tools: circleci/browser-tools@1.4.8
+
+jobs:
+  build-and-test:
+    # These next lines define a Docker executor: https://circleci.com/docs/2.0/executor-types/
+    # https://circleci.com/developer/images/image/cimg/node
+    docker:
+      - image: cimg/node:20.4.0-browsers
+    steps:
+      - checkout
+      - run:
+          name: NPM Install
+          command: npm install --force
+      - run:
+          name: Build Project
+          command: npm run build
+      - run:
+          name: Run tests
+          command: sleep 15 && npm run test
+
+workflows:
+  # Inside the workflow, you provide the jobs you want to run, e.g this workflow runs the build-and-test job above.
+  # CircleCI will run this workflow on every commit.
+  # https://circleci.com/docs/2.0/configuration-reference/#workflows
+  TestRunner:
+    jobs:
+      - build-and-test:
+          filters:
+            branches:
+              ignore:
+                # runs the github action
+                - release

package/.editorconfig

@@ -1,9 +1,9 @@
-
-root = true
-
-[*]
-trim_trailing_whitespace = true
-insert_final_newline = true
-indent_style = space
-indent_size = 4
+
+root = true
+
+[*]
+trim_trailing_whitespace = true
+insert_final_newline = true
+indent_style = space
+indent_size = 4
 quote_type = single

package/.github/workflows/npm-publish.yml

@@ -0,0 +1,30 @@
+# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
+# For more information see: https://docs.github.com/en/actions/publishing-packages/publishing-nodejs-packages
+
+name: Node.js Package
+
+on:
+  push:
+    branches:
+      - 'release'
+
+jobs:
+  build-test-publish:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          submodules: recursive
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 24
+          registry-url: 'https://registry.npmjs.org'
+          cache: npm
+
+      - run: npm ci
+      - run: npm run build
+      - run: npm run test
+      - run: npm publish --access public

package/README.md

@@ -1,33 +1,33 @@
-# HTML, Mask, JavaScript Application Bundler
-
-> Supports: `CommonJS`, [`MaskJS`](https://github.com/atmajs/maskjs), [`IncludeJS`](https://github.com/atmajs/includejs), `AMD`
-
-#### Why not ✨✨✨✨?
-
-With this module we try to follow these ideas:
-
-1. **No dependency**. The dev process and your app is not depended on bundler. So you would need to run this only for deployments. 
-
-2. **No configuration _(or few lines in packages.json)_**. You don't have hundred lines of configuration. 
-
-3. **Single responsibility**. We combine your modules in one or multple `JS`, `CSS` and `html` bundles.
-
-4. **Decoupled pre- and post-processing**. Bundler loads your files with [`atma-io`](https://github.com/atmajs/atma-io), which supports middlewares for file reads and writes. For example, this bundler handles only plain javascript modules, but you can choose any middleware to load files, for instance TypeScript files, which will be compiled on the fly. Same is also for css and templates.
-
-----
-
-# `1` CommonJS
-
-Build your CommonJS libraries and apps into one single module file.
-
-# `2` Web: `MaskJS`, `IncludeJS`, `AMD`
-
-The Application Bundler targets module systems, that do not require incremental builds. Have it simple: develop your web applications without any bundler, and then, only for production, build you app. No more huge `task` and `config` files.
-
-# `3` Preporcessors: `babel`, `less`, `scss`, `yml`, `typescript` and many more
-
-All preprocessors are decoupled from the Bundler. We use [`atma-io`](https://github.com/atmajs/atma-io) to load and write dependencies. That means, just include any file middleware as a plugin for `atma-io`.
-
-----
-
-:copyright: MIT
+# HTML, Mask, JavaScript Application Bundler
+
+> Supports: `CommonJS`, [`MaskJS`](https://github.com/atmajs/maskjs), [`IncludeJS`](https://github.com/atmajs/includejs), `AMD`
+
+#### Why not ✨✨✨✨?
+
+With this module we try to follow these ideas:
+
+1. **No dependency**. The dev process and your app is not depended on bundler. So you would need to run this only for deployments. 
+
+2. **No configuration _(or few lines in packages.json)_**. You don't have hundred lines of configuration. 
+
+3. **Single responsibility**. We combine your modules in one or multple `JS`, `CSS` and `html` bundles.
+
+4. **Decoupled pre- and post-processing**. Bundler loads your files with [`atma-io`](https://github.com/atmajs/atma-io), which supports middlewares for file reads and writes. For example, this bundler handles only plain javascript modules, but you can choose any middleware to load files, for instance TypeScript files, which will be compiled on the fly. Same is also for css and templates.
+
+----
+
+# `1` CommonJS
+
+Build your CommonJS libraries and apps into one single module file.
+
+# `2` Web: `MaskJS`, `IncludeJS`, `AMD`
+
+The Application Bundler targets module systems, that do not require incremental builds. Have it simple: develop your web applications without any bundler, and then, only for production, build you app. No more huge `task` and `config` files.
+
+# `3` Preporcessors: `babel`, `less`, `scss`, `yml`, `typescript` and many more
+
+All preprocessors are decoupled from the Bundler. We use [`atma-io`](https://github.com/atmajs/atma-io) to load and write dependencies. That means, just include any file middleware as a plugin for `atma-io`.
+
+----
+
+:copyright: MIT