IO.Console
in sigil v0.1.0
v0.1.0 is the oldest version of sigil that was analysed, so there is nothing to compare it against. IO.Console is a first sighting, not a change.
lib/build.march:3
1mod Build do
2
3 needs IO.Console
4
5 -- Wrapper for a user-supplied layout function.
6 -- Uses a nominal type to avoid March's curried function-type annotation ambiguity.
lib/deploy.march:5
2
3mod Deploy do
4
5 needs IO.Console
6
7 -- Deploy the build output directory to a Cloudflare Pages project.
8 -- Requires `wrangler` to be installed and authenticated:
lib/esbuild.march:6
3
4mod Esbuild do
5
6 needs IO.Console
7
8 -- Bundle an entry point (CSS or JS) to an output file.
9 -- Equivalent to: npx esbuild <entry> --bundle --outfile=<output>
lib/serve.march:3
1mod Serve do
2
3 needs IO.Console
4 needs IO.NetListen
5
6 pfn reload_script() : String do
lib/siteconfig.march:29
26
27mod SiteConfig do
28
29 needs IO.Console
30
31 -- Default config file name, looked up relative to the current working dir.
32 fn default_path() : String do "sigil.toml" end
lib/sigil.march:6
3
4mod Ssg do
5
6 needs IO.Console
7
8 fn parse_args(argv : List(String)) : Result(Config.Site, String) do
9 -- Drop the executable (and the script path in interpreted mode).
lib/watcher.march:3
1mod Watcher do
2
3 needs IO.Console
4
5 -- Read the output directory from the process environment.
6 -- The Serve module sets SIGIL_OUTPUT_DIR before starting the watcher.