From 2b5c2f0fc6e16705bddbfe043e90eef5eb31210b Mon Sep 17 00:00:00 2001 From: Matias Kinnunen Date: Sun, 8 Nov 2020 23:05:17 +0000 Subject: [PATCH] Fix inconsistent capitalizations of "JavaScript" (#2639) --- README.md | 2 +- ospec/README.md | 2 +- scripts/bundler-readme.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index b9bdb416..d76a0a27 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ mithril.js [![npm Version](https://img.shields.io/npm/v/mithril.svg)](https://ww ## What is Mithril? -A modern client-side Javascript framework for building Single Page Applications. It's small (9.79 KB gzipped), fast and provides routing and XHR utilities out of the box. +A modern client-side JavaScript framework for building Single Page Applications. It's small (9.79 KB gzipped), fast and provides routing and XHR utilities out of the box. Mithril is used by companies like Vimeo and Nike, and open source platforms like Lichess 👍. diff --git a/ospec/README.md b/ospec/README.md index 4a1227e6..b2fa93b1 100644 --- a/ospec/README.md +++ b/ospec/README.md @@ -662,6 +662,6 @@ Explicitly disallowing modularity and configuration in test-space has a few bene - tests always look the same, even across different projects and teams - single source of documentation for entire testing API -- no need to hunt down plugins to figure out what they do, especially if they replace common javascript idioms with fuzzy spoken language constructs (e.g. what does `.is()` do?) +- no need to hunt down plugins to figure out what they do, especially if they replace common JavaScript idioms with fuzzy spoken language constructs (e.g. what does `.is()` do?) - no need to pollute project-space with ad-hoc configuration code - discourages side-tracking and yak-shaving diff --git a/scripts/bundler-readme.md b/scripts/bundler-readme.md index 0b31883d..949d1ac9 100644 --- a/scripts/bundler-readme.md +++ b/scripts/bundler-readme.md @@ -11,7 +11,7 @@ This bundler attempts to aggressively bundle CommonJS modules by assuming the de Most browsers don't support ES6 `import/export` syntax, but we can achieve modularity by using CommonJS module syntax and transpiling it. -Webpack is conservative and treats CommonJS modules as non-statically-analyzable since `require` and `module.exports` are legally allowed everywhere. Therefore, it must generate extra code to resolve dependencies at runtime (i.e. `__webpack_require()`). Rollup only works with ES6 modules. ES6 modules can be bundled more efficiently because they are statically analyzable, but some use cases are difficult to handle due to ES6's support for cyclic dependencies and hosting rules. This bundler assumes code is written in CommonJS style but follows a strict set of rules that emulate statically analyzable code and favors the usage of the factory pattern instead of relying on obscure corners of the Javascript language (hoisting rules and binding semantics). +Webpack is conservative and treats CommonJS modules as non-statically-analyzable since `require` and `module.exports` are legally allowed everywhere. Therefore, it must generate extra code to resolve dependencies at runtime (i.e. `__webpack_require()`). Rollup only works with ES6 modules. ES6 modules can be bundled more efficiently because they are statically analyzable, but some use cases are difficult to handle due to ES6's support for cyclic dependencies and hosting rules. This bundler assumes code is written in CommonJS style but follows a strict set of rules that emulate statically analyzable code and favors the usage of the factory pattern instead of relying on obscure corners of the JavaScript language (hoisting rules and binding semantics). ### Caveats