app-bundler 0.2.21 → 0.2.23

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,37 +1,37 @@
1
- # See: https://circleci.com/docs/2.0/configuration-reference
2
- version: 2.1
3
-
4
- orbs:
5
- # See the orb documentation here: https://circleci.com/developer/orbs/orb/circleci/node
6
- browser-tools: circleci/browser-tools@1.4.8
7
-
8
- jobs:
9
- build-and-test:
10
- # These next lines define a Docker executor: https://circleci.com/docs/2.0/executor-types/
11
- # https://circleci.com/developer/images/image/cimg/node
12
- docker:
13
- - image: cimg/node:20.4.0-browsers
14
- steps:
15
- - checkout
16
- - run:
17
- name: NPM Install
18
- command: npm install --force
19
- - run:
20
- name: Build Project
21
- command: npm run build
22
- - run:
23
- name: Run tests
24
- command: sleep 15 && npm run test
25
-
26
- workflows:
27
- # Inside the workflow, you provide the jobs you want to run, e.g this workflow runs the build-and-test job above.
28
- # CircleCI will run this workflow on every commit.
29
- # https://circleci.com/docs/2.0/configuration-reference/#workflows
30
- TestRunner:
31
- jobs:
32
- - build-and-test:
33
- filters:
34
- branches:
35
- ignore:
36
- # runs the github action
37
- - release
1
+ # See: https://circleci.com/docs/2.0/configuration-reference
2
+ version: 2.1
3
+
4
+ orbs:
5
+ # See the orb documentation here: https://circleci.com/developer/orbs/orb/circleci/node
6
+ browser-tools: circleci/browser-tools@1.4.8
7
+
8
+ jobs:
9
+ build-and-test:
10
+ # These next lines define a Docker executor: https://circleci.com/docs/2.0/executor-types/
11
+ # https://circleci.com/developer/images/image/cimg/node
12
+ docker:
13
+ - image: cimg/node:20.4.0-browsers
14
+ steps:
15
+ - checkout
16
+ - run:
17
+ name: NPM Install
18
+ command: npm install --force
19
+ - run:
20
+ name: Build Project
21
+ command: npm run build
22
+ - run:
23
+ name: Run tests
24
+ command: sleep 15 && npm run test
25
+
26
+ workflows:
27
+ # Inside the workflow, you provide the jobs you want to run, e.g this workflow runs the build-and-test job above.
28
+ # CircleCI will run this workflow on every commit.
29
+ # https://circleci.com/docs/2.0/configuration-reference/#workflows
30
+ TestRunner:
31
+ jobs:
32
+ - build-and-test:
33
+ filters:
34
+ branches:
35
+ ignore:
36
+ # runs the github action
37
+ - release
package/.editorconfig CHANGED
@@ -1,9 +1,9 @@
1
-
2
- root = true
3
-
4
- [*]
5
- trim_trailing_whitespace = true
6
- insert_final_newline = true
7
- indent_style = space
8
- indent_size = 4
1
+
2
+ root = true
3
+
4
+ [*]
5
+ trim_trailing_whitespace = true
6
+ insert_final_newline = true
7
+ indent_style = space
8
+ indent_size = 4
9
9
  quote_type = single
package/README.md CHANGED
@@ -1,33 +1,33 @@
1
- # HTML, Mask, JavaScript Application Bundler
2
-
3
- > Supports: `CommonJS`, [`MaskJS`](https://github.com/atmajs/maskjs), [`IncludeJS`](https://github.com/atmajs/includejs), `AMD`
4
-
5
- #### Why not ✨✨✨✨?
6
-
7
- With this module we try to follow these ideas:
8
-
9
- 1. **No dependency**. The dev process and your app is not depended on bundler. So you would need to run this only for deployments.
10
-
11
- 2. **No configuration _(or few lines in packages.json)_**. You don't have hundred lines of configuration.
12
-
13
- 3. **Single responsibility**. We combine your modules in one or multple `JS`, `CSS` and `html` bundles.
14
-
15
- 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.
16
-
17
- ----
18
-
19
- # `1` CommonJS
20
-
21
- Build your CommonJS libraries and apps into one single module file.
22
-
23
- # `2` Web: `MaskJS`, `IncludeJS`, `AMD`
24
-
25
- 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.
26
-
27
- # `3` Preporcessors: `babel`, `less`, `scss`, `yml`, `typescript` and many more
28
-
29
- 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`.
30
-
31
- ----
32
-
33
- :copyright: MIT
1
+ # HTML, Mask, JavaScript Application Bundler
2
+
3
+ > Supports: `CommonJS`, [`MaskJS`](https://github.com/atmajs/maskjs), [`IncludeJS`](https://github.com/atmajs/includejs), `AMD`
4
+
5
+ #### Why not ✨✨✨✨?
6
+
7
+ With this module we try to follow these ideas:
8
+
9
+ 1. **No dependency**. The dev process and your app is not depended on bundler. So you would need to run this only for deployments.
10
+
11
+ 2. **No configuration _(or few lines in packages.json)_**. You don't have hundred lines of configuration.
12
+
13
+ 3. **Single responsibility**. We combine your modules in one or multple `JS`, `CSS` and `html` bundles.
14
+
15
+ 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.
16
+
17
+ ----
18
+
19
+ # `1` CommonJS
20
+
21
+ Build your CommonJS libraries and apps into one single module file.
22
+
23
+ # `2` Web: `MaskJS`, `IncludeJS`, `AMD`
24
+
25
+ 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.
26
+
27
+ # `3` Preporcessors: `babel`, `less`, `scss`, `yml`, `typescript` and many more
28
+
29
+ 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`.
30
+
31
+ ----
32
+
33
+ :copyright: MIT