complate / complate-stream Goto Github PK

View Code? Open in Web Editor NEW

6.0 2.0 7.0 124 KB

complate's core library for rendering HTML via JSX

Home Page: https://complate.org

JavaScript 99.49% Shell 0.51%

complate-stream's Introduction

complate-stream

complate's core library for rendering HTML

How It Works

At the core of complate-stream lies generateHTML, an implementation of the signature expected by JSX (as pioneered by React). When invoked, that function returns an "element generator"; a function serving as placeholder for the HTML element to be generated:

generateHTML("html", { lang: "en" },
        generateHTML("body", { id: "top" },
                generateHTML("h1", null, "hello world"),
                generateHTML("p", null, "lorem ipsum")));

This indirection is necessary primarily to ensure proper order and nesting, as function arguments are evaluated before the surrounding invocation – otherwise the code above would emit <h1> and <p> before the <body> and <html> elements.

Thus the example above returns a hierarchy of element generators, encapsulated by a single element generator at the root, which upon invocation writes HTML to the stream object being passed in:

let element = generateHTML(…);
element(stream, …);

(stream is expected to support the methods #write, #writeln and #flush; see BufferedStream for a sample implementation).

With our example, this should result in the following string being emitted:

<html lang="en"><body id="top"><h1>hello world</h1><p>lorem ipsum</p></body></html>

complate-stream's People

Contributors

Stargazers

Watchers

Forkers

mechanoid mechanoid-sandbox tillsc fride mkhl lsund tmehnert

complate-stream's Issues

An in-range update of faucet-pipeline-jsx is breaking the build 🚨

The devDependency faucet-pipeline-jsx was updated from `1.1.0` to `1.1.1`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

faucet-pipeline-jsx is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of eslint-config-fnd is breaking the build 🚨

Version 1.6.0 of eslint-config-fnd was just published.

Branch	Build failing 🚨
Dependency	eslint-config-fnd
Current Version	1.5.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

eslint-config-fnd is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of faucet-pipeline-jsx is breaking the build 🚨

The devDependency faucet-pipeline-jsx was updated from `2.0.6` to `2.0.7`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of esm is breaking the build 🚨

Version 3.0.58 of esm was just published.

Branch	Build failing 🚨
Dependency	esm
Current Version	3.0.57
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

esm is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 2 commits.

cf6076f Bump to v3.0.58.
e1321c2 Add missing wrapper args for Electron.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of faucet-pipeline-jsx is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 1.0.0-rc.1 of faucet-pipeline-jsx was just published.

Branch	Build failing 🚨
Dependency	faucet-pipeline-jsx
Current Version	1.0.0-beta.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Make `safe`and `HTMLString` idempotent

It should be possible to use safe(safe("some string")) to prevent stupid error messages.

documentation

Getting Started

choosing an adaptor
compiling views
creating and organizing views (e.g. views/manifest.js convention)

→ in-browser demo - see Bruck for a nicer editor experience, possibly even a proper editor

API

Examples

embeddable-content: minimal markup (container + link), PE results in augmented DOM thanks to custom element's client-side processing

Tips

JSX conventions: uppercase vs. lowercase, looping, Fragment
limited post-processing (unlike DOM) ⇒ explicit wrapping macros (e.g. <CardHeader> <h3> because if(children[0].tagName === "h3") { addWrapper(…); } doesn't work)
scalar vs. complex attributes

Internals

HTML generation (≙ generateHTML, JSX idiosyncrasies)
macros (≙ createElement, Renderer)

Background

rationale (abstraction & composition, cross-platform)
why streaming? (→ progressive rendering)
origin story
- decoupled BE vs. FE teams, in part due to tooling deficiencies ⇒ SPA ⇒ network API ⇒ awkward coupling and frustrating coordination
  resulted in experimenting (flailing) with Nashorn and servlets
- zero-runtime templating; JSX as DSL for function invocations
"complate" (suggested by tillsc)

Marketing

component-oriented templating
traditional templating does not sufficiently account for components (≈ abstraction + composition)
nutshell: generating static HTML, typically server-side rendering
"declarative rendering", "expressive, declarative UI components"
tech-agnostic (JS as lingua franca)
JSX for markup abstraction
JavaScript import semantics
testimonials
an example on Glitch might double as effective marketing
blurbs

if you're stuck on a JVM project but expect a suitable FE environment anyway

if you like React's developer workflow (modern front-end tooling), but are
unhappy with consequences for users (bloat, performance) and complexity
(SSR + rehydration)

Alternatives

Pug
- mixins for abstraction, ~~named blocks for composition~~
- implementations in various langauges, but with differences and thus limited portability? (e.g. versioning: uncertain whether Java implementation supports named blocks)
- global namespace for mixins? potentially brittle, also less explicit and flexible than JavaScript imports
Mustache:
- lacks abstraction/composition capabilities
- implementations in many langauges, but with differences and thus limited portability?
React SSR:
- same abstraction/composition capabilities
- client-side origins (e.g. state, component life cycle) might complicate debugging and overhead while browsing official documentation
- uncanny valley (e.g. className)
- runtime-agnosticism; Node only? (i.e. integration with other languages/runtimes would require a sidecar with a corresponding API - i.e. a contract specification between application and renderer - and thus additional overhead/complexity)

“Maximum call stack size exceeded” when trying to render large lists of items

We can reproduce complate/complate-spring-mvc#12 using only complate-stream by increasing the array size a bit.

Reproduction:

import Renderer, { createElement } from "complate-stream";
import BufferedStream from "./stream";

function ListView() {
	// simulating model property with large list
	let items = Array.apply(null, Array(10000)).map(function (_, i) {
		return i;
	});
	return createElement("ul", null,
		items.map(item => createElement("li", null, item)));
}

let renderer = new Renderer();
let stream = new BufferedStream();
renderer.renderView(ListView, null, stream);
console.log(stream.read());

An in-range update of esm is breaking the build 🚨

Version 3.0.55 of esm was just published.

Branch	Build failing 🚨
Dependency	`[esm](https://github.com/standard-things/esm)`
Current Version	3.0.54
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

3.0.55

Fixed V8 code cache usage regression

Commits

The new version differs by 4 commits.

a43595b Bump to v3.0.55.
2148b04 Update deps.
814324e Move "main" prefix so that the cache is generated from content with it.
7873756 Avoid unneeded cache invalidations.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of faucet-pipeline-jsx is breaking the build 🚨

The devDependency faucet-pipeline-jsx was updated from `2.0.8` to `2.0.9`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of esm is breaking the build 🚨

The devDependency esm was updated from `3.2.11` to `3.2.12`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 16 commits.

33cafee Bump to v3.2.12.
d6c6414 Update deps.
a0b2375 Don't project over custom console methods provided by the runtime. [closes #737]
d53f38d Var order nit.
fa8644d Remove @babel/register dirty cache guard.
8b8bcd1 Use fallback content for mod._compile() if provided.
3ea7eef Use setProperty() and toExternalFunction() when setting mod._compile().
d19a517 Use more toExternalError().
a183ab4 Mask errors in Module._preloadModules().
42115e9 Cleanup error masking branches.
fbb22d6 Move entry._passthruCompile reset to the same module it's set in.
4453156 Lint nit.
94a8e7c Track entry._ranthruCompile.
7a37941 Whitespace nit.
c42eaf1 Avoid running code through a possible transform pipeline when compile cached.

There are 16 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of eslint-config-fnd is breaking the build 🚨

The devDependency eslint-config-fnd was updated from `1.7.0` to `1.8.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of mocha is breaking the build 🚨

The devDependency mocha was updated from `6.1.4` to `6.2.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v6.2.0

6.2.0 / 2019-07-18

🎉 Enhancements

#3827: Do not fork child-process if no Node flags are present (@boneskull)
#3725: Base reporter store ref to console.log, see mocha/wiki (@craigtaub)

🐛 Fixes

#3942: Fix "No test files found" Error when file is passed via --file (@gabegorelick)
#3914: Modify Mocha constructor to accept options global or globals (@pascalpp)
#3894: Fix parsing of config files with _mocha binary (@juergba)
#3834: Fix CLI parsing with default values (@boneskull, @juergba)
#3831: Fix --timeout/--slow string values and duplicate arguments (@boneskull, @juergba)

📖 Documentation

#3906: Document option to define custom report name for XUnit reporter (@pkuczynski)
#3889: Adds doc links for mocha-examples (@craigtaub)
#3887: Fix broken links (@toyjhlee)
#3841: Fix anchors to configuration section (@trescube)

🔍 Coverage

#3915, #3929: Increase tests coverage for --watch options (@geigerzaehler)

🔩 Other

#3953: Collect test files later, prepares improvements to the --watch mode behavior (@geigerzaehler)
#3939: Upgrade for npm audit (@boneskull)
#3930: Extract runWatch into separate module (@geigerzaehler)
#3922: Add mocha.min.js file to stacktrace filter (@brian-lagerman)
#3919: Update CI config files to use Node-12.x (@plroebuck)
#3892: Rework reporter tests (@plroebuck)
#3872: Rename --exclude to --ignore and create alias (@boneskull)
#3963: Hide stacktrace when cli args are missing (@outsideris)
#3956: Do not redeclare variable in docs array example (@DanielRuf)
#3957: Remove duplicate line-height property in mocha.css (@DanielRuf)
#3960: Don't re-initialize grep option on watch re-run (@geigerzaehler)

Commits

The new version differs by 39 commits.

bd47776 Release v6.2.0
cc595af update CHANGELOG.md for v6.2.0 [ci skip]
59d70ee fix: remove duplicate line-height property (#3957)
f77cac4 fix: do not redeclare variable (#3956)
6201e42 Hide stacktrace when cli args are missing (#3963)
88f45d5 Don't re-initialize grep option on watch re-run (#3960)
5d4dd98 Fix No Files error when file is passed via --files (#3942)
15b96af Collect test files later (#3953)
ccee5f1 Base reporter store ref to console.log (#3725)
47318a7 update @mocha/contributors to v1.0.4 (#3944)
c903147 More, improved integration tests for watching (#3929)
e341ea4 Update CI config files to use Node-12.x (#3919)
3064d25 update @mocha/docdash to v2.1.1 (#3945)
9ea45e7 do not fork if no node flags present (#3827)
d02a096 modify Mocha constructor to accept options.global or options.globals (#3914)

There are 39 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

simplify stringification

cf. a4afcf0

import { createElement } from "complate-stream";
import BufferedStream from "complate-stream/src/buffered-stream";

let stream = new BufferedStream();
let element = MyMacro();
element(stream, { nonBlocking: true }, () => {
    let html = stream.read();
    …
});

this is a bit clunky and non-obvious, so we might simply provide a utility function to take care of all that:

stringify(MyMacro, params, ...children).
    then(html => …);

`renderView` should accept optional `...children`

There should be an additional parameter ...children in renderView to allow passing children from somewhere else into the view-macro. This can be useful when utilizing external layout mechanisms like done in complate-ruby.

An in-range update of esm is breaking the build 🚨

Version 3.0.53 of esm was just published.

Branch	Build failing 🚨
Dependency	`[esm](https://github.com/standard-things/esm)`
Current Version	3.0.52
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

3.0.53

Ensured line continuations work in the REPL (#476)
Fixed regression with esm compiled into Node

Commits

The new version differs by 15 commits.

87061af Bump to v3.0.53.
0ae18da Fix appveyor test fail.
52afcbc Add compile tests for parse errors.
1462b8f Add more V8 style error messages.
37d07e1 Use createCachedData() in ./esm.js when available.
36167f0 Normalize unterminated string error.
f639607 Split out acorn/parser/error-messages from acorn/parser/tolerance.
2563edc Upgrade deps.
a5052d6 Destructure more prototype properties.
cf47e83 Fix test fails in node-chakracore.
19ad6fb Align syntax error messates more closely to V8. [closes #476]
3cd3a7e Destructure prototype properties.
e05c149 Use Script#creatCachedData() when available.
235f96e Move processing pendingScripts until the end of the process.
d6b4c3b Fix native Node path in ./esm.js.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of faucet-pipeline-jsx is breaking the build 🚨

Version 1.0.0-rc.8 of faucet-pipeline-jsx was just published.

Branch	Build failing 🚨
Dependency	faucet-pipeline-jsx
Current Version	1.0.0-rc.7
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of npm-run-all is breaking the build 🚨

The devDependency npm-run-all was updated from `4.1.3` to `4.1.4`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

npm-run-all is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 3 commits.

a79fbac 🔖 4.1.4
d97929c remove test in version script temporary
57d72eb 🔥 remove ps-tree

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of faucet-pipeline-jsx is breaking the build 🚨

Version 1.0.0-beta.1 of faucet-pipeline-jsx was just published.

Branch	Build failing 🚨
Dependency	faucet-pipeline-jsx
Current Version	1.0.0-beta.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

complate must warn if macro doesn't return anything

A common mistake is forgetting the return like this

export default () => {
  <span></span>
}

This leads to strange errors.

The check must be applied here:

complate-stream/src/renderer.js

Line 73 in ed85dae

let element = createElement(macro, params);

rename to complate-html

That seems more expressive and also consistent WRT complate-dom.

An in-range update of esm is breaking the build 🚨

Version 3.0.72 of esm was just published.

Branch	Build failing 🚨
Dependency	esm
Current Version	3.0.71
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 56 commits.

e174d2c Bump to v3.0.72.
7ea979c Update deps.
3ac6065 Comment defaultPkg clone usage.
3e689b1 Add Package#clone() to dry out code.
f555bce Style nits for stdio.
88c40b6 Use adaptive wait times for pm2 test.
92fba74 Avoid realpathSync.native use in Electron.
21953fb Cleanup main hook tests.
c85ed55 Add main hook tests to ensure execution.
7c22f88 Revert "Remove unneeded package options cloning." [closes #504]
0062ac1 Var name nit in path/normalize.
c59f8ca Fix Node 6 test fail due to trailing comma.
c2c618f Remove unused getWarning() function from misc-tests.
37ebbf3 Fix test fail in Windows.
67e0644 Ensure request query/fragments can contain encoded slashes. [closes #512]

There are 56 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

allow safe strings from different languages than JS

When using other languages than JS:

It would be nice to pass "native" strings into complate marked as safe. complate should accept those Strings as HTMLStrings.

We should discuss this.

An in-range update of esm is breaking the build 🚨

Version 3.0.19 of esm was just published.

Branch	Build failing 🚨
Dependency	esm
Current Version	3.0.18
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

3.0.19

Ensured modules aren’t cached in Module._cache before Module._load is called (#362)

Commits

The new version differs by 23 commits.

4358c29 Bump to v3.0.19.
a530f5b Update webpack.
8b13798 Remove unneeded sqreen tip.
76d64b2 Only iterate over own-keyed parseCache entries.
2837eb3 Var placement nits.
56ea66a Newline nit.
4bf77c9 Add sqreen scenario tests.
43a308b Test description nit.
c11acd3 Add getURLFromFilePath() to shared.module cache.
6c4b8b1 Defer resolving import.meta.url until import.meta is created.
2b6de3e Stop tracking entry.url.
b3b74b0 Set entry and module properties as soon as possible.
81a1be9 Remove unneeded var assignment in module/esm/resolve-filename.
5699a57 Use getModuleURL() in maskStackTrace().
a5d3400 Move util/has-encoded-slash to path/has-encoded-sep.

There are 23 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of esm is breaking the build 🚨

Version 3.0.65 of esm was just published.

Branch	Build failing 🚨
Dependency	esm
Current Version	3.0.64
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

3.0.65

Improved console, eval, and TDZ transforms

Commits

The new version differs by 13 commits.

0f3d2f9 Bump to v3.0.65.
0fdfc75 Update eslint.
477c314 Add more console and eval compiler tests.
c72fb19 Ensure eval is transformed as an argument.
3824de8 Add compiler tests for TDZ and eval when shadowed by catch, default, and rest params.
1b5ee03 Check CatchClause in isShadowed().
3cd3c15 Inline getExportedInspect() helper in src/util/inspect.
06797c2 Inline getConsole() helper in src/builtin/global.
639284f Reduce nesting in isShadow().
922e4e1 Use getNamesFromPattern() in isShadowed().
8e15d19 Include AssignmentPattern in assignment guard of isIdentifier().
c5ec30b Add console compile tests.
0ffd4b4 Add finalizer, superClass, and update to childrenToVisit.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of esm is breaking the build 🚨

The devDependency esm was updated from `3.2.18` to `3.2.19`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 29 commits.

2941c50 Bump to v3.2.19.
0c9700a Update deps.
40651a8 Make builtin-errors expose more stack.
90fa0c1 Cleanup matches().
a7859b4 Remove -m alias detection from FLAGS.type.
5b5eba9 Add FLAGS.experimentalJSONModules.
1ea356b Rename Runtime._runResult to Runtime.runResult.
427cc17 Cleanup cjsVars compile options assignment in Runtime.compileEval() and Runtime.compileGlobalEval().
40bf1e0 Don't clip stack traces of parse/syntax errors.
bc3b212 Newline nits.
4e6d73e Don't use URLs in stack traces if options.cjs.paths is true.
d8dcf0d Update mocha link to require options (#758)
1d93fb3 Add util.format() and util.formatWithOptions() tests.
e411656 Add copyright header to src/util/format.
371e752 Add type guard to safeFormatWithOptions.

There are 29 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

review HTML encoding

perhaps use he instead of relying on our own, somewhat half-baked implementation?

complate / complate-stream Goto Github PK

complate-stream's Introduction

complate-stream

How It Works

complate-stream's People

Contributors

Stargazers

Watchers

Forkers

complate-stream's Issues

The devDependency faucet-pipeline-jsx was updated from 1.1.0 to 1.1.1.

Version 1.6.0 of eslint-config-fnd was just published.

The devDependency faucet-pipeline-jsx was updated from 2.0.6 to 2.0.7.

Version 3.0.58 of esm was just published.

Version 1.0.0-rc.1 of faucet-pipeline-jsx was just published.

Getting Started

API

Examples

Tips

Internals

Background

Marketing

Alternatives

Version 3.0.55 of esm was just published.

The devDependency faucet-pipeline-jsx was updated from 2.0.8 to 2.0.9.

The devDependency esm was updated from 3.2.11 to 3.2.12.

The devDependency eslint-config-fnd was updated from 1.7.0 to 1.8.0.

The devDependency mocha was updated from 6.1.4 to 6.2.0.

6.2.0 / 2019-07-18

🎉 Enhancements

🐛 Fixes

📖 Documentation

🔍 Coverage

🔩 Other

Version 3.0.53 of esm was just published.

Version 1.0.0-rc.8 of faucet-pipeline-jsx was just published.

The devDependency npm-run-all was updated from 4.1.3 to 4.1.4.

Version 1.0.0-beta.1 of faucet-pipeline-jsx was just published.

Version 3.0.72 of esm was just published.

Version 3.0.19 of esm was just published.

Version 3.0.65 of esm was just published.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

The devDependency esm was updated from 3.2.18 to 3.2.19.

Recommend Projects

Recommend Topics

Recommend Org

Jobs

The devDependency faucet-pipeline-jsx was updated from `1.1.0` to `1.1.1`.

The devDependency faucet-pipeline-jsx was updated from `2.0.6` to `2.0.7`.

The devDependency faucet-pipeline-jsx was updated from `2.0.8` to `2.0.9`.

The devDependency esm was updated from `3.2.11` to `3.2.12`.

The devDependency eslint-config-fnd was updated from `1.7.0` to `1.8.0`.

The devDependency mocha was updated from `6.1.4` to `6.2.0`.

The devDependency npm-run-all was updated from `4.1.3` to `4.1.4`.

The devDependency esm was updated from `3.2.18` to `3.2.19`.