Skip to content

fix: enable deno_core feature for JavaScript expression evaluation#134

Merged
oleksandr-nc merged 1 commit intonextcloud:mainfrom
strobelpierre:fix/enable-deno-core-feature
Feb 9, 2026
Merged

fix: enable deno_core feature for JavaScript expression evaluation#134
oleksandr-nc merged 1 commit intonextcloud:mainfrom
strobelpierre:fix/enable-deno-core-feature

Conversation

@strobelpierre
Copy link
Contributor

Summary

  • Enable the deno_core Cargo feature when building Windmill to fix JavaScript expression evaluation in workflows

Problem

Since version 1.3.0, users get the error:

ExecutionErr: Error during isolated evaluation of expression: Deno core is not enabled

This happens because the deno_core Cargo feature was not enabled when building Windmill. This feature is required for Windmill to evaluate JavaScript/TypeScript expressions in workflows (e.g., flow_input.event.values[0].value[0].id).

Solution

Add deno_core to the features build argument in the Makefile:

  • --build-arg features=python--build-arg features=deno_core,python

The deno_core feature enables the embedded JavaScript runtime based on deno_core and V8. This is different from the external Deno binary (/usr/bin/deno) which is already included in the image.

Test plan

  • Build the Docker image with make init && make build-amd64
  • Verify that JavaScript expressions in workflows evaluate correctly without the "Deno core is not enabled" error

Fixes #129

Since version 1.3.0, users get the error:
"ExecutionErr: Error during isolated evaluation of expression: Deno core is not enabled"

This happens because the `deno_core` Cargo feature was not enabled when building
Windmill. This feature is required for Windmill to evaluate JavaScript/TypeScript
expressions in workflows (e.g., `flow_input.event.values[0].value[0].id`).

The `deno_core` feature enables the embedded JavaScript runtime based on deno_core
and V8. This is different from the external Deno binary (`/usr/bin/deno`) which is
already included in the image.

Fixes nextcloud#129

Signed-off-by: Strobel Pierre <strobelpierre@gmail.com>
@strobelpierre strobelpierre force-pushed the fix/enable-deno-core-feature branch from 4916568 to 19f260a Compare February 3, 2026 15:13
@tareko
Copy link

tareko commented Feb 7, 2026

I'm testing this particular fix, and it appears to work for the core issue.

@pyranota
Copy link

pyranota commented Feb 8, 2026

It might also need other features enabled in there, python and deno_core is relatively small sub-set of what windmill offers.

Copy link
Contributor

@oleksandr-nc oleksandr-nc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for looking into this issue and offering a solution

@oleksandr-nc oleksandr-nc merged commit 96b3681 into nextcloud:main Feb 9, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1.3.0 - Windmill: Deno core is not enabled

4 participants