Forge cli is resource hungry and other forge topics

Forge Forge Platform and Tools
1

Hi all!

I was wondering if I am the only one who has several issues with the CLI of Forge.

Namely:

  1. > 30% CPU (1 core) usage when idle
  2. Takes sometimes more than 20 seconds to lint/bundle and be ready (even for small typo-like changes)
  3. The “hack” to deploy license check does not work

My projects uses only UIKit (3) has several handlers and 1 daily cron.
Node version: 20.18.1
Forge/cli: 10.13.1

For 1)

For 2), I have the impression that the “watcher” gets lost at some point and runs in circle several times, especially when I have multiple modified files. I don’t use eslint to reformat on save, I use biome which is faster.
Is Forge missing some sort of implementation of a grace period before triggering the rebuild job?
Is there a way to reduce the linting processing to only check for things that might break the build?

For 3), I’m referring to test license documentation that I have never been able to see work. (env variable or argument)

Thanks in advance for your feedback

2 Likes
2

Hmm…
<troll>
It must be that I have a bad setup (i.e. “not a mac”).
</troll>

Seriously though, nobody from the Atlassian team here ? Nobody is interested in feedback.

Do I really have to open a ticket for each and every issue I run across while working with Forge ? Knowing that is take days or weeks to arrive to somebody vaguely interested…

1 Like
3

Hi @MagnusAnderssen,

Thank you for bringing this to our attention. Could you please create a support ticket for the issue using the following link: Jira Service Management. This approach will help you track progress more effectively and ensure that all teams are aligned. It will also facilitate better communication and a quicker resolution time. Once you’ve created the ticket, please share it here as well. Thank you!

Best regards,
Chandana

4

hmmm… ok, let’s see if that works better

➙ CPU usage
➙ Slow to compile