Will this project continue to be maintained?

[mamo2021]

The last updates were made years ago. I have also not found a fork that is still being maintained.
When trying to install the instance using docker-compose, the following message is displayed:

ERROR: for ethercalc [DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of docker.io/audreyt/ethercalc:latest to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/

Is Ethercalc still being developed and kept up to date or is the project dead?

[1n5aN1aC]

It appears that the author has an alternative docker hub image which is updated for the new(er) docker format. It still appears pretty old, and no recent updates, but it does run without any further modifications:

https://hub.docker.com/r/audreyt/ethercalc-4.8

image: audreyt/ethercalc-4.8

[rophy]

I managed to upgrade nodejs to 18, fix critical CVEs by manaually, minimally force upgrade some packages, and rewrite Dockerfile to not rely on the ancient published npm package:

master...rophy:ethercalc:fix-critical-cve

The docker image works for me: node 18, no critical CVE, mult-user spreadsheet works. I built one and published to: https://hub.docker.com/r/rophy/ethercalc/tags

However, to make this project really maintainable, I think we need to drop that livescript and use more modern technology.

From ethercalc blog, livescript was adopted to deal with nodejs callback hell and "prototype things with less lines of code"...

1. callback hell is no longer an issue thanks to async / await.
2. Less lines of code doesn't mean it's easier to maintain, sadly this project turnd out to be the opposite.

I tried to spend a day doing that, and gave up for now due to some complexity involved:

1. zappajs went through major incompatible changes, instead of adapting to new version, may consider finding alternatives given it was a framework for coffeescript, which is even more ancient than livescript.
2. webpack had incompatible changes as will, have to revamp the build flow.
3. Build flow for multi/main.ls seems to be broken related to multi/styles.styl. Things still work because compiled main.js is also in git. At a glance, I'm not sure how to fix that.

[eddyparkinson]

I think we need to drop that livescript and use more modern technology.

I found the live script easy enough after I discovered this page:
https://livescript.net/

The last updates were made years ago.

I think this is true of the majority of git hub projects.

In the past people have cloned it for use in other projects. The code is the best open source JS spreadsheet code I know of.

[ocdtrekkie]

There are a few rough edges I hit as a daily user but I started using it ten years ago and it's still pretty great.