Step 1

Parse

$ARGUMENTS

:

First token →

If a second token looks like a URL (starts with

http

) →

(standalone mode); remaining tokens →

[project-root]

Otherwise →

[project-root]

(consumer mode)

Step 2 — consumer mode

(no URL provided):

Call the

mf-context

Skill (passing

[project-root]

) to collect MFContext, then run:

node

scripts/module-info.js

--context

''

--module

''

Step 2 — standalone mode

(URL provided):

Run with an empty context and the explicit URL:

node

scripts/module-info.js

--context

'{}'

--module

''

--url

''

Step 3

Present the

result

from the script output:

Field

Description

publicPath

Base URL of the remote

remoteEntry

Full URL to

remoteEntry.js

typesZip

URL to

@mf-types.zip

typesApi

URL to

@mf-types.api

(shown only if present)

hasSsr

Whether SSR build artifacts were detected

exposes

Modules this remote exposes

remotes

Remotes this module depends on

shared

Shared dependencies declared by this module

If

result.error

is set, surface it directly and stop.

Step 4 (conditional)

If the user explicitly asks to see the type declarations (e.g. "show me the types", "what types does it export"), fetch result.typesZip or result.typesApi and display the relevant type definitions.