@curiostack/base-web 0.2.2

Bug fixes

• Picture tag does not output extraneous comment text into DOM

Breaking changes

• curio-image-loader exports the image descriptor directly instead of as a default export, so e.g., require('image.png?lossy&xs=100') must be used without specifying .default

@curiostack/base-web 0.2.1

New Features

• babel-plugin-macros is enabled so you can use libraries that use macros
• @curiostack/tsconfig has been published with the standard CurioStack TypeScript configuration. You can remove tsconfig.json from the top level of your repository and instead of extending it at project level tsconfig.json, extend this published version instead

{
  "extends": "@curiostack/tsconfig",
  "include": [
    "src/**/*"
  ],
  "compilerOptions": {
    "baseUrl": "."
  }
}

It's unclear why include / baseURL can't be set in the parent configuration, in the future this may be fixed to reduce boilerplate further.

• @curiostack/base-web now exports common types for non-JS modules (e.g., json, png). Most projects will currently have a types.d.ts with many of these definitions but now you can do this instead

/* eslint-disable spaced-comment */

/// <reference types="@curiostack/base-web" />

See this example and the definited types here

If you see any types that would be useful for most users, please contribute to this types file!

Breaking changes

ESLint advanced typescript checking is enabled. You will probably need to add a parser option to your eslintrc. If you are using JSON, you must change it to JS.

module.exports = {
  extends: '@curiostack/web',
  parserOptions: {
    tsconfigRootDir: __dirname,
  },
};

curiostack-0.4.4

This release fixes a breakage introduced during the recent upgrade to Armeria. All users should use 0.4.4 instead of previous versions.

Bug Fixes

• Fixes issue where clients are not initialized correctly

curiostack-0.4.2

Bug fixes

• Fixes a inssue with protobuf not extracting protos correctly from project dependencies

Improvements

• Automatically adds mockito-junit-jupiter to test dependencies of Java projects

curiostack-0.4.1

Bug fixes

• Apply curiostack-bom to legacy compile and testCompile configurations to allow migration
• gradle-protobuf-plugin uses e.g. compileClasspath instead of compile for resolving dependencies for compatibility with new configurations
• Test configurations have target JVM version set to 11 to allow them to use Java 11, even for Java 8 modules

curiostack-0.4.0

Improvements

• Published projects now use Gradle to populate resolved versions instead of manually resolving versions in the XML
• Better error messaging in armeria-google-cloud-storage
• curio-test-framework now configures JUnit5 with a default timeout of 10s. If you have tests that take longer than this, they will begin to fail until you add @Timeout

Bug fixes

• Conda failed to execute in IntelliJ on Windows

Breaking changes

• Armeria 0.98.1 contains many breaking changes on its way to 1.0. Check its release notes for details. Most breakage you will find in your code will be when accessing RequestContext attributes.

@curiostack/base-web-0.1.2

Bug fixes

• An issue in 0.1.0 preventing reducers or sagas from being ready during a component's componentDidMount lifecycle method has been fixed.

Deprecations

• The injectReducer and injectSaga HOCs have been deprecated. Switch to hooks and useReducer and useSaga. The HOCs will be removed with the release of React 17.

curiostack-0.3.0

This release only contains dependency updates. Notable updates are to Armeria and Error Prone

Breaking Changes

• Error prone has been updated, introducing new checks. These will generally break a build until dealt with. Two that affected the Curiostack codebase are PreferJavaTimeOverload and UnnecessaryLambda. Unfortunately, due to Error Prone's lack of support for Java 12+, you will usually encounter cryptic stack traces due to these checks. This happens when error prone tries to suggest a fix for the issue. Since the check name itself shows up despite this, you should be able to fix the build by addressing the check or suppressing it.

Security fixes

• Armeria 0.97.0 includes two security fixes. Curiostack rates both issues as Low severity - quickly upgrading is not required. The timing issue is infeasible outside a contrived setting, and the header injection issue only affects HTTP/1. Curiostack users should be serving all requests with HTTP/2, including those from browsers as they are proxied by GCP's HTTP/2 load balancers, so are not affected by the issue.

@curiostack/base-web-0.1.1

Updates dependencies, notably including a fix for a security vulnerability in serialize-javascript - GHSA-h9rv-jmmf-4pgx

The expected severity for curiostack users of this is low, as it would require using regex objects in redux state, which is not a normal pattern.

curiostack-0.2.0

This release only contains dependency updates. However, it includes an update to Armeria with significant breaking changes. You will need some time to update your apps.

Breaking Changes

• You will need to replace all uses of HttpClient and decorators in your codebase. It tends to help the refactor to have IntelliJ structural replace new HttpClientBuilder with WebClient.newBuilder() before replacing other usages of the type.

Please see https://github.com/line/armeria/releases/tag/armeria-0.96.0 for details.

FYI

Previously, pluginManagement or buildscript tweaking was required due to missing packages on jcenter. The syncing issue has been fixed so this should no longer be necessary.