gleam export package-interface produces empty modules object

[bcpeinhardt]

When I run gleam export package-interface --out <some_path>.json on any of my packages (tested with simplifile and gsv),
the file produced has an empty object for the modules field as though they were empty packages.

{"name":"gsv","version":"1.4.0","gleam-version-constraint":">= 0.32.0","modules":{}}

I checked the package-interface.json in the build directory and it's being correctly produced, so the module info get's lost somehow exporting the file.

I'm on an M2 Mac running the main branch of Gleam. The logs from after the compile stage are pretty sparse

Compiled in 0.01s
TRACE writing_file path="/Users/benjaminpeinhardt/Development/Projects/gsv/./file.json"
INFO Successfully completed

I'll try and look into this as I bet it's something small or I'm doing something wrong, but if someone beats me to it I won't be upset haha.

[PgBiel]

Running gleam clean before the export seems to restore the correct behavior for me (once, but not for subsequent runs). It appears to only work if something was compiled.

[lpil]

@giacomocavalieri am I right in thinking you fixed this? Or did I make that up?

[giacomocavalieri]

No I haven't (or at least not knowingly)! I should check whether this happens on the main branch as well

[PgBiel]

I think it's this TODO here:

gleam/compiler-core/src/build/package_compiler.rs

Lines 85 to 89 in 176334c

	/// Compile the package.
	/// Returns a list of modules that were compiled. Any modules that were read
	/// from the cache will not be returned.
	// TODO: return the cached modules.
	pub fn compile(

[TanklesXL]

hmmm this was closed as completed but I'm still able to replicate this behaviour on gleam 1.4 🤔 should we reopen this issue?

[TanklesXL]

@lpil sorry to bug you. Just wanted to follow up on what was discussed in discord. This issue is confirmed to be unresolved and should be reopened 😃

[lpil]

Thank you