"Barrel already resolved" for "barrels.jungle" copy when optimizing project from the command line

[m4tiz5zktonj]

1. Clone https://github.com/markw65/Barrels.
2. Copy DataFieldWithBarrels/barrels.jungle to DataFieldWithBarrels/custom-barrels.jungle.
3. Create optimize.mjs from https://github.com/markw65/monkeyc-optimizer/blob/main/README.md.
4. Fix const workspace = path.dirname(jungleFiles); with const workspace = path.dirname(jungleFiles.split(";")[0]);.
5. Install @markw65/monkeyc-optimizer.
6. Run node optimize.mjs ".../DataFieldWithBarrels/monkey.jungle;.../DataFieldWithBarrels/custom-barrels.jungle".

Result:

Error: Barrel BarrelTest already resolved to .../BarrelTest/monkey.jungle; can't also resolve to .../BarrelTest/monkey.jungle

Observations:

1. Command node optimize.mjs ".../DataFieldWithBarrels/monkey.jungle;.../DataFieldWithBarrels/barrels.jungle" finishes without errors.
2. Command node optimize.mjs ".../DataFieldWithBarrels/monkey.jungle;.../DataFieldWithBarrels/custom-barrels.jungle" finishes without errors if .../DataFieldWithBarrels/barrels.jungle doesn't exist.
3. Command line monkeyc doesn't fail with non-default barrels.jungle name.

[markw65]

Ok... I'm just not sure what to do about it. The monkeyc compiler does something to automatically pull in barrels.jungle when it's needed - but I'm not sure what.

A simple fix would be to not add "barrels.jungle" if more than one jungle file is specified on the command line. But you could include the barrel references in your main jungle file, so...

I'm somewhat inclined to just say don't put a barrels.jungle file next to your monkey.jungle file unless you want pmc to use it.

What's the correct behavior here?

[m4tiz5zktonj]

The monkeyc compiler does something to automatically pull in barrels.jungle when it's needed

Does it? If I build freshly cloned DataFieldWithBarrels project without any modifications on my part, Garmin's Monkey C plugin will indeed add barrels.jungle to monkeyc call despite the "monkeyC.jungleFiles": "monkey.jungle". If I execute the command line printed by Garmin's plugin without specifying barrels.jungle in -f argument (and without deleting the file itself), build will fail due to the missing resources from the barrel. It seems to me that monkeyc doesn't use any jungles implicitly, but VS Code plugin does if barrels.jungle is present.

I'm somewhat inclined to just say don't put a barrels.jungle file next to your monkey.jungle file unless you want pmc to use it.

JFYI, this is the case where I need to have separate jungle files for tests and for debug/release/export builds, so it seems natural to me to have multiple monkey/barrels jungle files in the project root (just as others have multiple manifest.xml for beta/production apps), but I understand if you can't or don't want to support that. Yeah, I probably can't use custom-barrels.jungle with Garmin's plugin, but it's not an issue since 99% of time I run monkeyc (and now monkeyc-optimizer) directly.

What's the correct behavior here?

Ideally, PMC could match Garmin's plugin behavior and include barrels.jungle in prettier-extension-monkeyc instead of monkeyc-optimizer, but it's hard to say how significant the impact of these changes would be.

Thanks for all your work!