protoscript - npm Package Versions

v0.0.10

• Change configuration file format. Now, the configuration file is JS instead of JSON. This provides better discoverability and type checking for TypeScript users.

The following .protoscript.json:

{
  "root": "src",
};

Would be renamed to proto.config.mjs and changed to the following:

/** @type {import('protoscript').Config} */
export default {
  root: "src",
};

• Use relative file path for determining path to compiler instead of hard coding from project root. This should interop better with more exotic package tooling and repo setup.

• Fix: Improved map detection. Previously field types suffixed with Entry were incorrectly flagged as maps. This has been fixed.

v0.0.9

• Remove process.stdin.fd usage to see if it resolves intermittent Error: EAGAIN: resource temporarily unavailable, read. See #191 for more context.

v0.0.8

• Use ["property"] access for JSON objects. This ensures generated JSON serialization code is correct when using minification tools that perform property mangling. See #4 for more context.

v0.0.7

• Include file extensions in generated file imports.

v0.0.6

• Distribute strict ESM. A CommonJS is runtime is included for legacy node clients. Code generation uses ESM and requires Node.js v14 or later.

v0.0.20

• Preserve protoscript import when well known types are imported. This corrects a regression in 0.0.19.

v0.0.19

• Fix JSON serializtion for Timestamp and Duration well known types. See #39.
• Accept all value permutations as described by the Proto3 JSON spec when parsing JSON messages.
• #initialize now accepts partial messages. This enables you to create a full message with select fields set to a user-provided value:

  const ron = User.initialize({ firstName: "Ron" });