Git Product home page Git Product logo

dev-config's Introduction

Stencila

Programmable, reproducible, interactive documents

πŸ‘‹ Intro β€’ 🚴 Roadmap β€’ πŸ“œ Docs β€’ πŸ“₯ Install β€’ πŸ› οΈ Develop

πŸ™ Acknowledgements β€’ πŸ’– Supporters β€’ πŸ™Œ Contributors



πŸ‘‹ Introduction

Stencila is a platform for creating and publishing, dynamic, data-driven content. Our aim is to lower the barriers for creating truly programmable documents, and to make it easier to publish them as beautiful, interactive, and semantically rich, articles and applications. Our roots are in scientific communication, but our tools are useful beyond.

This is v2 of Stencila, a rewrite in Rust focussed on the synergies between three recent and impactful innovations and trends:

We are embarking on a rewrite because CRDTs will now be the foundational synchronization and storage layer for Stencila documents. This requires fundamental changes to most other parts of the platform. Furthermore, a rewrite allow us to bake in, rather than bolt on, new modes of interaction between authors and LLM assistants and add mechanisms to mitigate the risks associated with using LLMs (e.g. by recording the actor, human or LLM, that made the change to a document). Much of the code in the v1 branch will be reused (after some tidy-ups and refactoring), so v2 is not a complete rewrite.

🚴 Roadmap

Our general strategy is to iterate horizontally across the feature set, rather than fully developing features sequentially. This will better enable early user testing of workflows and reduce the risk of finding ourselves painted into an architectural corner. So expect initial iterations to have limited functionality and be buggy.

We'll be making alpha and beta releases of v2 early and often across all products (e.g. CLI, desktop, SDKs). We're aiming for a 2.0.0 release by the end of Q3 2024.

🟒 Stable β€’ πŸ”Ά Beta β€’ ⚠️ Alpha β€’ 🚧 Under development β€’ πŸ§ͺ Experimental β€’ 🧭 Planned β€’ ❔ Maybe

Schema

The Stencila Schema is the data model for Stencila documents (definition here, generated reference documentation here). Most of the schema is well defined but some document node types are still marked as under development. A summary by category:

Category Description Status
Works Types of creative works (e.g. Article, Figure, Review) 🟒 Stable (mostly based on schema.org)
Prose Types used in prose (e.g. Paragraph, List, Heading) 🟒 Stable (mostly based on HTML, JATS, Pandoc etc)
Code Types for executable (e.g. CodeChunk) and non-executable code (e.g. CodeBlock) πŸ”Ά Beta (may change)
Math Types for math symbols and equations (e.g. MathBlock) πŸ”Ά Beta (may change)
Data Fundamental data types (e.g. Number) and validators (e.g. NumberValidator) πŸ”Ά Beta (may change)
Flow Types for control flow within a document (e.g. If, For, Call) πŸ”Ά Beta (may change)
Style Types for styling parts of a documents (Span and Division) πŸ”Ά Beta (may change)
Edits Types related to editing a documents (e.g. InstructionBlock, DeleteInline) πŸ”Ά Beta (may change)

Storage and synchronization

In v2, documents can be stored as binary Automerge CRDT files, branched and merged, and with the ability to import and export the document in various formats. Collaboration, including real-time, is made possible by exchanging fine-grained changes to the CRDT over the network. In addition, we want to enable interoperability with a Git-based workflow.

Functionality Description Status
Documents read/write-able Able to write a Stencila document to an Automerge binary file and read it back in ⚠️ Alpha
Documents import/export-able Able to import or export document as alternative formats, using tree diffing to generate CRDT changes ⚠️ Alpha
Documents fork/merge-able Able to create a fork of a document in another file and then later merge with the original 🧭 Planned
Documents diff-able Able to view a diff, in any of the supported formats, between versions of a document and between a document and another file 🧭 Planned
Git merge driver CLI can act as a custom Git merge driver 🧭 Planned
Relay server Documents can be synchronized by exchanging changes via a relay server 🧭 Planned
Rendezvous server Documents can be synchronized by exchanging changes peer-to-peer using TCP or UDP hole punching ❔ Maybe

Formats

Interoperability with existing formats has always been a key feature of Stencila. We are bringing over codecs (a.k.a. converters) from the v1 branch and porting other functionality from encoda to Rust.

Format Encoding Decoding Coverage Notes
JSON 🟒 🟒
JSON5 🟒 🟒
JSON-LD 🟒 🟒
CBOR 🟒 🟒
CBOR+Zstandard 🟒 🟒
YAML 🟒 🟒
Plain text πŸ”Ά -
HTML 🚧 🧭
JATS 🚧 🚧 Planned for completion. Port decoding and tests from encoda.
Markdown ⚠️ ⚠️
R Markdown 🧭 🧭 Relies on Markdown; v1
Myst Markdown 🚧 🚧 In progress; PR
Jupyter Notebook 🧭 🧭 Relies on Markdown; v1
Scripts 🧭 🧭 Relies on Markdown; v1
Pandoc 🧭 🧭 Planned. v1
LaTeX 🧭 🧭 Relies on Pandoc; v1; discussion
Org 🧭 🧭 Relies on Pandoc; PR
Microsoft Word 🧭 🧭 Relies on Pandoc; v1
ODT 🧭 🧭 Relies on Pandoc
Google Docs 🧭 🧭 Planned v1
PDF 🧭 🧭 Planned, relies on HTML; v1
Codec Plugin API 🧭 🧭 An API allowing codecs to be developed as plugins in Python, Node.js, and other languages

Kernels

Kernels are what executes the code in Stencila CodeChunks and CodeExpressions, as well as in control flow document nodes such as ForBlock and IfBlock. In addition, there are kernels for rendering math (e.g. MathBlock) and styling (e.g. StyledInline) nodes.

Kernel Purpose Status
Bash Execute Bash code πŸ”Ά Beta
Zsh Execute Zsh code ❔ Maybe; v1
Python Execute Python code πŸ”Ά Beta
R Execute R code ⚠️ Alpha
QuickJs Execute JavaScript in embedded sandbox πŸ”Ά Beta
Node.js Execute JavaScript in a Node.js env πŸ”Ά Beta
Deno Execute TypeScript code ❔ Maybe; v1
SQLite Execute SQL code 🧭 Planned; v1
Jupyter kernels Execute code in Jupyter kernels 🚧 In progress; PR
Rhai Execute a sand boxed, embedded language πŸ”Ά Beta
AsciiMath Render AsciiMath symbols and equations πŸ”Ά Beta
TeX Render TeX math symbols and equations πŸ”Ά Beta
Graphviz Render Graphviz DOT to SVG images ⚠️ Beta
Jinja Interpolate document variables into styling and other code ⚠️ Beta
Style Transpile Tailwind and CSS for styling πŸ”Ά Beta
HTTP Interact with RESTful APIs ❔ Maybe; v1

[TIP] Run stencila kernels (or cargo run -p cli kernels in development) for an up to date list of kernels, including those available through plugins.

Tools

Tools are what we call the self-contained Stencila products you can download and use locally on your machine to interact with Stencila documents.

Environments Purpose Status
CLI Manage documents from the command line and read and edit them using a web browser ⚠️ Alpha
Desktop Manage, read and edit documents from a desktop app ⚠️ Alpha repo
VSCode extension Manage, read and edit documents from within VSCode ⚠️ Alpha

SDKs

Stencila's software development kits (SDKs) enable developers to create plugins to extend Stencila's core functionality or to build other tools on top of. At this stage we are planning to support Python, Node.js and R but more languages may be added if there is demand.

Language Description Status Coverage
Python Types and function bindings for using Stencila from Python ⚠️ Alpha PyPI
TypeScript JavaScript classes and TypeScript types for the Stencila Schema ⚠️ Alpha NPM
Node.js Types and function bindings for using Stencila from Node.js ⚠️ Alpha NPM

Testing and auditing

Making sure Stencila v2 is well tested, fast, secure, and accessible, is important. Here's what where doing towards that:

What Description Status
Property-based testing Establish property-based (a.k.a generative) testing for Stencila documents 🟒 Done
Round-trip testing Establish property-based tests of round-trip conversion to/from supported formats and reading/writing from/to Automerge CRDTs 🟒 Done here and here
Coverage reporting Report coverage by feature (e.g. by codec) to give developers better insight into the status of each 🟒 Done Codecov
Dependency audits Add dependency audits to continuous integration workflow. 🟒 Done
Accessibility testing Add accessibility testing to continuous integration workflow. 🟒 Done here
Performance monitoring Establish continuous benchmarking 🟒 Done here
Security audit External security audit sponsored by NLNet. 🧭 Planned Q2 2023 (after most v2 functionality added and before public beta)
Accessibility audit External accessibility audit sponsored by NLNet. 🧭 Planned Q3 2023 (before v2.0.0 release)

πŸ“œ Documentation

At this stage, documentation for v2 is mainly reference material, much of it generated:

More reference docs as well as guides and tutorial will be added over the coming months. We will be bootstrapping the publishing of all docs (i.e. to use Stencila itself to publish HTML pages) and expect to have an initial published set in.

πŸ“₯ Install

Although v2 is in early stages of development, and functionality may be limited or buggy, we are releasing alpha versions of the Stencila CLI and SDKs. Doing so allows us to get early feedback and monitor what impact the addition of features has on build times and distribution sizes.

CLI

Windows

To install the latest release download stencila-<version>-x86_64-pc-windows-msvc.zip from the latest release and place it somewhere on your PATH.

MacOS

To install the latest release in /usr/local/bin,

curl --proto '=https' --tlsv1.2 -sSf https://stencila.dev/install.sh | sh

To install a specific version, append -s vX.X.X. Or, if you'd prefer to do it manually, download stencila-<version>-x86_64-apple-darwin.tar.gz from the one of the releases and then,

tar xvf stencila-*.tar.gz
cd stencila-*/
sudo mv -f stencila /usr/local/bin # or wherever you prefer
Linux

To install the latest release in ~/.local/bin/,

curl --proto '=https' --tlsv1.2 -sSf https://stencila.dev/install.sh | sh

To install a specific version, append -s vX.X.X. Or, if you'd prefer to do it manually, download stencila-<version>-x86_64-unknown-linux-gnu.tar.gz from the one of the releases and then,

tar xvf stencila-*.tar.gz
mv -f stencila ~/.local/bin/ # or wherever you prefer
Docker

The CLI is also available in a Docker image you can pull from the Github Container Registry,

docker pull stencila/stencila

and use locally like this for example,

docker run -it --rm -v "$PWD":/work -w /work --network host stencila/stencila --help

The same image is also published to the Github Container Registry if you'd prefer to use that,

docker pull ghcr.io/stencila/stencila

SDKs

Python

Use your favorite package manager to install Stencila's SDK for Python:

python -m pip install stencila

[!NOTE] If you encounter problems with the above command, you may need to upgrade Pip using pip install --upgrade pip.

poetry add stencila
Node

Use your favorite package manager to install @stencila/node:

npm install @stencila/node
yarn add @stencila/node
pnpm add @stencila/node
TypeScript

Use your favorite package manager to install @stencila/types:

npm install @stencila/types
yarn add @stencila/types
pnpm add @stencila/types

πŸ› οΈ Develop

Code organization

This repository is organized into the following modules. Please see their respective READMEs, where available, for guides to contributing to each.

  • schema: YAML files which define the Stencila Schema, an implementation of, and extensions to, schema.org, for programmable documents.

  • json: A JSON Schema and JSON LD @context, generated from Stencila Schema, which can be used to validate Stencila documents and transform them to other vocabularies

  • rust: Several Rust crates implementing core functionality and a CLI for working with Stencila documents.

  • python: A Python package, with classes generated from Stencila Schema and bindings to Rust functions, so you can work with Stencila documents from within Python.

  • ts: A package of TypeScript types generated from Stencila Schema so you can create type-safe Stencila documents in the browser, Node.js, Deno etc.

  • node: A Node.js package, using the generated TypeScript types and bindings to Rust functions, so you can work with Stencila documents from within Node.js.

  • prompts: Prompts for used to instruct AI assistants in different contexts and for different purposes.

  • docs: Documentation, including reference documentation generated from schema and CLI tool.

  • examples: Examples of documents conforming to Stencila Schema, mostly for testing purposes.

  • scripts: Scripts used for making releases and during continuous integration.

Continuous integration and deployment

Several Github Action workflows are used for testing and releases. All products (i.e CLI, Docker image, SKDs) are released at the same time with the same version number. To create and release a new version:

bash scripts/bump-version.sh <VERSION>
git push && git push --tags
Workflow Purpose Status
test.yml Run linting, tests and other checks. Commit changes to any generated files.
pages.yml Publish docs, JSON-LD, JSON Schema, etc to https://stencila.dev hosted on GitHub Pages
version.yml Trigger the release.yml workflow when a version tag is created.
release.yml Create a release, including building and publishing CLI, Docker image and SDKs.
install.yml Test installation and usage of CLI, Docker image and SDKs across various operating systems and language versions.

πŸ™ Acknowledgements

Stencila is built on the shoulders of many open source projects. Our sincere thanks to all the maintainers and contributors of those projects for their vision, enthusiasm and dedication. But most of all for all their hard work! The following open source projects in particular have an important role in the current version of Stencila. We sponsor these projects where, and to an extent, possible through GitHub Sponsors and Open Collective.

Link Summary
Automerge A Rust library of data structures for building collaborative applications.
Clap A Command Line Argument Parser for Rust.
NAPI-RS A framework for building pre-compiled Node.js addons in Rust.
PyO3 Rust bindings for Python, including tools for creating native Python extension modules.
Rust A multi-paradigm, high-level, general-purpose programming language which emphasizes performance, type safety, and concurrency.
Serde A framework for serializing and deserializing Rust data structures efficiently and generically.
Similar A Rust library of diffing algorithms including Patience and Hunt–McIlroy / Hunt–Szymanski LCS.
Tokio An asynchronous runtime for Rust which provides the building blocks needed for writing network applications without compromising speed.

πŸ’– Supporters

We wouldn’t be doing this without the support of these forward looking organizations.

πŸ™Œ Contributors

Thank you to all our contributors (not just the ones that submitted code!). If you made a contribution but are not listed here please create an issue, or PR, like this.

Ackerley Tng Aleksandra Pawlik Alex Ketch Ben Shaw Colette Doughty Daniel Beilinson Daniel Ecer
Daniel Mietchen Daniel NΓΌst Danielle Robinson Dave David Moulton Finlay Thompson FΓ‘bio H. K. Mendes
J Hunt Jacqueline James Webber Jure Triglav Lars Willighagen Mac Cowell Markus Elfring
Michael Aufreiter Morane Gruenpeter MorphicResonance Muad Abd El Hay Nokome Bentley Oliver Buchtala Raniere Silva
Remi Rampin Rich Lysakowski Robert Gieseke Seth Vincent Stefan Fritsch Suminda Sirinath Salpitikorala Dharmasena Tim McNamara
Titus Tony Hirst Uwe Brauer Vanessasaurus Vassilis Kehayas alexandr-sisiuc asisiuc
campbellyamane ern0 - Zalka ErnΕ‘ grayflow happydentist huang12zheng ignatiusm jmhuang
jon r kitten solsson taunsquared yasirs

dev-config's People

Contributors

alex-ketch avatar dependabot[bot] avatar nokome avatar renovate-bot avatar renovate[bot] avatar stencila-ci avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

dev-config's Issues

Improve install message

Some improvements could be made to the install message:

  • make it more visible (c.f. the husky one above)
  • fix the typo in "package"
  • don't have it double up
  • ensure quotes around require(... (as in the first) so that the command can be copied and pasted

image

Enable no-shadow ESLint rule

A tangential note for the JS, I think we should enable the ESLint no-shadow rule to avoid bugs and simplifying process for reading code.

Originally posted by @alex-ketch in stencila/thema#84


Motivation: From the rule reference

Shadowing is the process by which a local variable shares the same name as a variable in its containing scope. For example:

var a = 3;
function b() {
   var a = 10;
}

In this case, the variable a inside of b() is shadowing the variable a in the global scope. This can cause confusion while reading the code and it's impossible to access the global variable.

Issue upgrading dev-config: upstream dependency conflict

When attempting to upgrade to the latest version of @stencila/dev-config I have been getting the following error:

npm install
npm WARN ERESOLVE overriding peer dependency
npm WARN Found: @typescript-eslint/[email protected]
npm WARN node_modules/@typescript-eslint/parser
npm WARN   @typescript-eslint/parser@"^4.23.0" from @stencila/[email protected]
npm WARN   node_modules/@stencila/eslint-config
npm WARN     @stencila/eslint-config@"2.0.9" from @stencila/[email protected]
npm WARN     node_modules/@stencila/dev-config
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @typescript-eslint/parser@"^2.23.0" from @stencil/[email protected]
npm WARN node_modules/@stencila/eslint-config/node_modules/@stencil/eslint-plugin
npm WARN   @stencil/eslint-plugin@"^0.3.1" from @stencila/[email protected]
npm WARN   node_modules/@stencila/eslint-config
npm WARN ERESOLVE overriding peer dependency
npm WARN Found: @typescript-eslint/[email protected]
npm WARN node_modules/@typescript-eslint/eslint-plugin
npm WARN   @typescript-eslint/eslint-plugin@"^4.23.0" from @stencila/[email protected]
npm WARN   node_modules/@stencila/eslint-config
npm WARN     @stencila/eslint-config@"2.0.9" from @stencila/[email protected]
npm WARN     node_modules/@stencila/dev-config
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @typescript-eslint/eslint-plugin@"^2.23.0" from @stencil/[email protected]
npm WARN node_modules/@stencila/eslint-config/node_modules/@stencil/eslint-plugin
npm WARN   @stencil/eslint-plugin@"^0.3.1" from @stencila/[email protected]
npm WARN   node_modules/@stencila/eslint-config
npm WARN ERESOLVE overriding peer dependency
npm WARN Found: [email protected]
npm WARN node_modules/eslint
npm WARN   eslint@"^7.26.0" from @stencila/[email protected]
npm WARN   node_modules/@stencila/eslint-config
npm WARN     @stencila/eslint-config@"2.0.9" from @stencila/[email protected]
npm WARN     node_modules/@stencila/dev-config
npm WARN   3 more (@typescript-eslint/parser, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer eslint@"^6.0.0" from @stencil/[email protected]
npm WARN node_modules/@stencila/eslint-config/node_modules/@stencil/eslint-plugin
npm WARN   @stencil/eslint-plugin@"^0.3.1" from @stencila/[email protected]
npm WARN   node_modules/@stencila/eslint-config
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: [email protected]
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"4.3.2" from the root project
npm ERR!   peer typescript@"^3.5.3 || ^4.0.0" from @stencila/[email protected]
npm ERR!   node_modules/@stencila/eslint-config
npm ERR!     @stencila/eslint-config@"2.0.9" from @stencila/[email protected]
npm ERR!     node_modules/@stencila/dev-config
npm ERR!       dev @stencila/dev-config@"2.0.12" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@"^3.8.0" from @stencil/[email protected]
npm ERR! node_modules/@stencila/eslint-config/node_modules/@stencil/eslint-plugin
npm ERR!   @stencil/eslint-plugin@"^0.3.1" from @stencila/[email protected]
npm ERR!   node_modules/@stencila/eslint-config
npm ERR!     @stencila/eslint-config@"2.0.9" from @stencila/[email protected]
npm ERR!     node_modules/@stencila/dev-config
npm ERR!       dev @stencila/dev-config@"2.0.12" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /home/nokome/.npm/eresolve-report.txt for a full report.

Here is a recent example from Encoda, but I have also noticed it when trying to install @stencila/dev-config in stencila/stencila/viewer:

https://dev.azure.com/stencila/stencila/_build/results?buildId=12787&view=logs&j=ad07b744-5a1a-5d54-7693-fcb02e666633&t=88540a4e-0b51-541f-e623-7b2636eab300&l=83

Update dependencies

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

These problems occurred while renovating this repository. View logs.

  • WARN: Using npm packages for Renovate presets is now deprecated. Please migrate to repository-based presets instead.

Warning

These dependencies are deprecated:

Datasource Name Replacement PR?
npm @stencil/eslint-plugin Unavailable
npm eslint-plugin-node Available
npm write-pkg Unavailable

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

  • chore(dependencies): replace dependency eslint-plugin-node with eslint-plugin-n >=11.0.0

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

Detected dependencies

github-actions
.github/workflows/publish.yml
  • actions/checkout v3
  • actions/setup-node v3
npm
package.json
  • @commitlint/config-conventional 16.2.4
  • commitlint 16.3.0
  • husky 7.0.4
  • lerna 4.0.0
  • prettier 2.8.8
  • pretty-quick 3.3.1
packages/dev-config/package.json
  • @commitlint/config-conventional >=13.0.0
  • commitlint >=13.0.0
  • prettier >=2.4.1
  • pretty-quick >=3.1.1
  • write-pkg >=5.0.0
packages/eslint-config-stencil/package.json
  • @stencil/eslint-plugin >=0.4.0
  • eslint-config-prettier >=8.0.0
  • eslint-config-standard >=16.0.0
  • eslint-plugin-import >=2.0.0
  • eslint-plugin-jsx-a11y >=6.0.0
  • eslint-plugin-node >=11.0.0
  • eslint-plugin-prettier >=4.0.0
  • eslint-plugin-promise >=5.0.0
  • eslint-plugin-react ^7.0.0
  • prettier >=2.0.0
  • typescript ^4.0.8
packages/eslint-config/package.json
  • @typescript-eslint/eslint-plugin >=5.0.0
  • eslint >=7.0.0
  • eslint-config-prettier >=8.0.0
  • eslint-config-standard >=17.0.0-0
  • eslint-plugin-import >=2.0.0
  • eslint-plugin-node >=11.0.0
  • eslint-plugin-prettier >=4.0.0
  • eslint-plugin-promise >=5.0.0
  • prettier >=2.0.0
  • typescript >=4.0.0
packages/renovate-config/package.json
packages/semantic-release-config-gh-pages/package.json
  • @qiwi/semantic-release-gh-pages-plugin ^5.0.4
  • @semantic-release/changelog ^6.0.0
  • @semantic-release/commit-analyzer ^9.0.0
  • @semantic-release/git ^10.0.0
  • @semantic-release/github ^8.0.0
  • @semantic-release/npm ^9.0.0
  • @semantic-release/release-notes-generator ^10.0.0
  • semantic-release ^19.0.0
  • semantic-release ^18.0.0 || ^19.0.2
packages/semantic-release-config/package.json
  • @semantic-release/changelog ^6.0.0
  • @semantic-release/commit-analyzer ^9.0.0
  • @semantic-release/git ^10.0.0
  • @semantic-release/github ^8.0.0
  • @semantic-release/npm ^9.0.0
  • @semantic-release/release-notes-generator ^10.0.0
  • semantic-release ^19.0.0
  • semantic-release ^18.0.0 || ^19.0.2

  • Check this box to trigger a request for Renovate to run again on this repository

Semantic release not updating version in package.json

Semantic release is creating a git tag and updating CHANGELOG, but is not updating the version in package.json. This affects all our repos using @stencila/semantic-release-config. For example in Encoda:

nokome@pluto ~/s/s/encoda (master)> git describe --tags
v0.60.3
nokome@pluto ~/s/s/encoda (master)> cat package.json | grep version
  "version": "0.59.2",

The current version in package.json was updated by me manually, some time ago when I first noticed this bug.

It can be confirmed to be due to moving to using this repo:

  • in commit 4c9add1b2b2be574a88f0d792158112c21c846a1 stencila-ci incremented the version in package.json and added the v0.50.0 git tag
  • in the next commit 3b6ac04bf5749a0b18f6f0645fa1a03d40ee3589 we changed the semantic release config to be "extends": "@stencila/semantic-release-config"
  • in the next release f13405229432735cc52b24a66dc3fe61fd1499c5 the CHANGELOG is updated, but not package.json

I think this may have to do with how https://github.com/semantic-release/npm resolves which package.json to update.

fix(Semantic Release): Fails if `docs` folder is not present

From this PR:

There is a risk that this will fail the whole release if a docs folder is not present in the repo. But most of our repos use that pattern (?) and if not, then the config can be overridden to specify to source folder, or perhaps skip this plugin.

From this build:

[4:09:55 AM] [semantic-release] β€Ί βœ–  An error occurred while running semantic-release: { Error: docs source directory does not exist

Renovate configuration

An issue to collect ideas / notes on the our renovate-config. Perhaps the main strength of Renovate is how configurable it is. However, that can at time make it difficult to understand.

  • Currently "stabilityDays": 3 - a PR still gets created, but frustratingly the "stability days check" fails - would be better to combine with prCreation="not-pending" so the PR does not get created at all. Also, for @stencila packages the days should probably be 0. See https://docs.renovatebot.com/configuration-options/#stabilitydays

  • Currently prod deps have "rangeStrategy": "bump", but it seems like that does not have any advantages over "pin" - just keeps the caret ^ prefix

  • Currently prod deps are not grouped - which is great for being able to ascertain which deps are causing failures and isolate them. But it does potentially lead to many patch release on the same day - unless, like I do, you merge them locally and then push.

  • We could reduce our maintenence time by using automerging (when tests pass): could start using that for dev deps and prod deps in repos that are well tested e.g. (logga)

@typescript-eslint/strict-boolean-expressions overly strict

I find the @typescript-eslint/strict-boolean-expressions lint rule a bit painful and have turned it off in Encoda because it makes heavy use of expressions like variable && variable.prop and variable || 'default'.

I cant' find a good rationale for this rule, especially for null and undefined. The TSLint docs, whence this rule came, offer no insight: https://palantir.github.io/tslint/rules/strict-boolean-expressions/.

Others also think this rule is too strict by default typescript-eslint/typescript-eslint#698. I suggest that until some of those options are available that we remove this rule.

Simplify `dev-config` packages

To make upgrading dependent projects easier, as well as avoid bringing in unnecessary dependencies in other projects we should explore using dependencies field, and instead use peerDependencies.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.