Build Issues [Mac, with yarn v24.2.0]

[dsynkd]

⚠️ Check issue is valid.

• My request is about the Tasks plugin for Obsidian.

⚠️ Check that this issue hasn't been reported before.

• I searched previous Tasks plugin Bug Reports didn't find any similar reports.

Steps to reproduce

Running yarn outputs the following:

yarn install v1.22.22
error SyntaxError: Invalid value type 1781:0 in /Users/dsynkd/Repositories/fork/obsidian-tasks/yarn.lock
    at Parser.unexpected (/opt/homebrew/lib/node_modules/yarn/lib/cli.js:64026:11)
    at Parser.parse (/opt/homebrew/lib/node_modules/yarn/lib/cli.js:64154:16)
    at Parser.parse (/opt/homebrew/lib/node_modules/yarn/lib/cli.js:64131:26)
    at parse (/opt/homebrew/lib/node_modules/yarn/lib/cli.js:64231:21)
    at module.exports.exports.default (/opt/homebrew/lib/node_modules/yarn/lib/cli.js:63793:96)
    at Lockfile.<anonymous> (/opt/homebrew/lib/node_modules/yarn/lib/cli.js:3068:63)
    at Generator.next (<anonymous>)
    at step (/opt/homebrew/lib/node_modules/yarn/lib/cli.js:310:30)
    at /opt/homebrew/lib/node_modules/yarn/lib/cli.js:321:13
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

npm i works fine though.

Running yarn dev also does not work:

yarn run v1.22.22
$ node esbuild.config.mjs
error TS5102: Option 'importsNotUsedAsValues' has been removed. Please remove it from your configuration.
  Use 'verbatimModuleSyntax' instead.
error TS5102: Option 'preserveValueImports' has been removed. Please remove it from your configuration.
  Use 'verbatimModuleSyntax' instead.

✘ [ERROR] [plugin esbuild-svelte] [svelte-preprocess] Encountered type error

    src/Obsidian/TaskModal.ts:3:21:
      3 │ import EditTask from '../ui/EditTask.svelte';
        ╵                      ~~~~~~~~~~~~~~~~~~~~~~~

1 error
[watch] build finished, watching for changes...
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
~~

Expected Behavior

Installation and build commands should not produce errors.

Current behaviour

There are installation errors.

Which Operating Systems are you using?

• Android
• iPhone/iPad
• Linux
• macOS
• Windows

Obsidian Version

1.9.7

Tasks Plugin Version

7.20

Checks

• I have tried it with all other plugins disabled and the error still occurs

Possible solution

Upgrade "@tsconfig/svelte" to "^5.0.4".

[claremacrae]

What versions of node and yarn are you using?

This works for me on Mac:

obsidian-tasks git:(main) node --version
v20.15.1
obsidian-tasks git:(main) yarn --version
1.22.19

[claremacrae]

Updating to Svelte 5 is out of the question currently. We are on 3, and that's two major breaking version changes, so definitely not a priority.

[claremacrae]

I am not familiar with this command:

yarn install v1.22.22

I am used to just running yarn.

[claremacrae]

The links here may help:
https://publish.obsidian.md/tasks-contributing/Building/About+Building

[claremacrae]

I do not expect use of npm will work, as it will ignore the pinned version numbers in yarn.lock, that Tasks is built, tested and released against.

[claremacrae]

error SyntaxError: Invalid value type 1781:0 in /Users/dsynkd/Repositories/fork/obsidian-tasks/yarn.lock

That line seems very suspicious to me. Have you got any edits in your fork?

There is definitely nothing wrong with line 1781 in yarn.lock on main:

obsidian-tasks/yarn.lock

Line 1781 in 055564e

[dsynkd]

I am not familiar with this command:

yarn install v1.22.22

I am used to just running yarn.

The error shown was for just running yarn, yarn install v1.22.22 is the first line of the output.

Updating to Svelte 5 is out of the question currently. We are on 3, and that's two major breaking version changes, so definitely not a priority.

My suggestion was only meant to include the tsconfig upgrade.

The links here may help: https://publish.obsidian.md/tasks-contributing/Building/About+Building

The instructions here say to check package.json for which version of Node to use, and package.json says to use "node": ">=18.0.0". I had v24.2.0. I tried using switching to your version v20.15.1withnvm`, and now everything works. Maybe we should put that as the currently required node version?

[claremacrae]

Ok good.

Yes, if it were possible to pin down the working ranges and adjust the limits in package.json, that would be a very welcome PR.