GitHub

Things needed to hit a 1.0 candidate release, and would ideally demonstrate that Greenwood can establish and solid and stable API for multiple project archetypes; SPA, SSG, SSR, or SSG / SSR hybrid and different hosting environments and runtimes like NodeJS, Edge and Serverless functions, Deno, etc.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

1.0

feature and plugin deprecations

inline <code><script></code> and <code><style></code> tags should get processed by Greenwood standard resource plugins

configuration lifecycle is running excessively (related to custom loaders usage?)

routine maintenance and semver major upgrades of key dependencies

data client is not rehydrating from existing WINDOW.APOLLO_STATE on initial load

enable a logging level configuration flag

reduce duplicate fetches for cache.json by storing in client.js memory

html minification

PWA Capability

source maps are missing content (source files) when using inline optimization setting

enable throttling of max number of pages that can be prerendered at once

create Lit specific polyfill plugin

add support for (progressive) hydration for compatible renderers

SSR and API routes should support dynamic route naming (with prerendering)

performance benchmarking / optimizing Greenwood

apply isomorphic standards to userland libraries and plugins (<code>globalThis</code>)

Support Web Assembly format

handle default <code>Content-Type</code> being set in default <code>Response</code> instances

static router outputting a <code><script></code> tag with a path of <code>/undefined</code> (when an SSR route is present?)

ensure proper termination of server plugins when Greenwood process ends

move import maps shim to polyfills plugin

implement a more idiomatic (HTML) templating solution

Cloudflare Adapter plugin

support additional <code>Request.body</code> formats

Isomorphic Asset Bundling

1.0

List view