@jsenv/core 38.2.5 → 38.2.6

package/README.md

@@ -1,6 +1,6 @@
 # @jsenv/core [![npm package](https://img.shields.io/npm/v/@jsenv/core.svg?logo=npm&label=package)](https://www.npmjs.com/package/@jsenv/core)
 
-Jsenv is a tool to develop test and build projects using JavaScript. Jsenv is simple, easy to understand and well [documented](<https://github.com/jsenv/core/wiki/A)-directory-structure>).
+Jsenv is a tool to develop test and build projects using JavaScript. Jsenv is simple, easy to understand and well documented.
 
 Jsenv cares a lot about the developper experience, especially when it comes to tests.
 
@@ -11,23 +11,11 @@ The pillars of jsenv are:
 3. A build server serving build files
 4. A test runner executing test files in web browser(s)
 
-# The best parts
-
-## Reduce cognitive load inside test files
-
-When coding, we spend most of our time working on source files. At some point we switch from source files to test files. Suddenly things are different:
-
-- code does not execute as it would in source files
-- some tools are used differently in test files, some cannot be used at all
-- you are forced to code in a certain way that is completely different from the one in source files
+[Link to documentation](<https://github.com/jsenv/core/wiki/A)-directory-structure>)
 
-This huge gap between source files and test files creates a context switching costing a lot of cognitive energy.  
-Jsenv makes a special effort to [provide a solution](<https://github.com/jsenv/core/wiki/D)-Test>) where switching from source files to test files is easy.
-
-It also means tools used on source files can be reused on test files: ESlint, VSCode debugger, etc. No need to maintain separate tools and/or configurations.
-
-## Other good parts
+# The best parts
 
+- Tools and habits used in source files [can be reused in test files](<https://github.com/jsenv/core/wiki/D)-Test>).
 - A [large browser support during dev](<https://github.com/jsenv/core/wiki/B)-Dev#21-browser-support>). Because some people might be happy to use an other browser than the latest chrome during dev. Moreover it is useful to reproduce bug specific to certain browsers.
 - A [large browser support after build](<https://github.com/jsenv/core/wiki/C)-Build#211-maximal-browser-support>). Because some product still needs to support old versions of Firefox, Chrome and Safari.
 - A [single set of files during build](<https://github.com/jsenv/core/wiki/C)-Build#212-same-build-for-all-browsers>). Because a single one is simpler to properly support in every aspects.
@@ -35,7 +23,7 @@ It also means tools used on source files can be reused on test files: ESlint, VS
 - Ability to [execute tests in multiple browsers](<https://github.com/jsenv/core/wiki/D)-Test#32-executing-on-more-browsers>): Chrome, Safari, Firefox
 - An advanced support of top level await, allowing to use it everywhere
 - An advanced support of web workers including worker type module
-- Unlock js module features on a regular `<script>` when needed. If you need the behaviour of `<script>` which is to block other `<script>` tag in the page, you'll be happy to still have the power of js modules, like imports, at your disposal.
+- Unlock js module features on a regular `<script>` when needed. If you need the behaviour of `<script>` which is to block execution of following `<script>` in the page, you'll be happy to [still have the power of js modules](<https://github.com/jsenv/core/wiki/G)-Plugins#22-asjsclassic>), like imports, at your disposal.
 
 # Demos
 
@@ -57,7 +45,7 @@ It will prompt to choose one of the available demo:
     node-package
 ```
 
-Selecting "web" will copy [create-jsenv/demo-web](https://github.com/jsenv/core/tree/bc7fb0aa2c8ced1db4d7583a2ea1858be464c23b/packages/related/create-jsenv/demo-web)<sup>↗</sup> files into a directory:
+Selecting "web" will copy [create-jsenv/demo-web](https://github.com/jsenv/core/tree/bc7fb0aa2c8ced1db4d7583a2ea1858be464c23b/packages/related/create-jsenv/demo-web) files into a directory:
 
 ```console
 ✔ Select a demo: › web
@@ -71,9 +59,6 @@ npm start
 
 After running the suggested commands the demo is ready.
 
-> **Info**
-> "npm install" can take time because tests are runned in headless browsers that needs to be installed first.
-
 The demo contains preconfigured scripts:
 
 - `npm run dev`: starts a server for source files; Documented in [B) Dev](<https://github.com/jsenv/core/wiki/B)-Dev>).

package/dist/jsenv_core.js

@@ -3857,6 +3857,7 @@ const createLog = ({
     write,
     dynamicWrite,
     destroy,
+    stream,
   });
   return log;
 };
@@ -3891,7 +3892,7 @@ const startSpinner = ({
   stopOnVerticalOverflow = true,
   render = () => "",
   effect = () => {},
-  animated = true,
+  animated = log.stream.isTTY,
 }) => {
   let frameIndex = 0;
   let interval;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jsenv/core",
-  "version": "38.2.5",
+  "version": "38.2.6",
   "description": "Tool to develop, test and build js projects",
   "license": "MIT",
   "author": {
@@ -65,13 +65,13 @@
     "@jsenv/filesystem": "4.3.2",
     "@jsenv/importmap": "1.2.1",
     "@jsenv/integrity": "0.0.1",
-    "@jsenv/log": "3.4.0",
+    "@jsenv/log": "3.4.1",
     "@jsenv/node-esm-resolution": "1.0.1",
     "@jsenv/js-module-fallback": "1.3.5",
     "@jsenv/runtime-compat": "1.2.0",
-    "@jsenv/server": "15.1.2",
+    "@jsenv/server": "15.1.3",
     "@jsenv/sourcemap": "1.2.3",
-    "@jsenv/plugin-bundling": "2.5.4",
+    "@jsenv/plugin-bundling": "2.5.5",
     "@jsenv/plugin-minification": "1.5.2",
     "@jsenv/plugin-transpilation": "1.3.4",
     "@jsenv/plugin-supervisor": "1.3.4",