How Fiber is structuredAn interactive map of the Fiber codebase. The Express inspired Go web framework, the whole repo in 414 files, most of them middleware. app.go stands out at twelve times a typical file here.

Files visualized: 414

Languages: Go

Topics: web framework, go

Source repository: https://github.com/gofiber/fiber

Structure414 files and 468 connections between their symbols.Most depended on

client/errors.go, imported by 100 files

log/context.go, imported by 67 files

log/log.go, imported by 35 files

internal/tlstest/tls.go, imported by 22 files

binder/json.go, imported by 17 files

Files

client/errors.go: no top-level classes or functions; imports internal/logtemplate/errors.go

log/context.go: 2 classes, 10 functions; imports client/errors.go, internal/contextvalue/contextvalue.go

log/log.go: 5 classes, 1 function

internal/tlstest/tls.go: 1 function; imports client/errors.go

binder/json.go: 1 class, 2 functions

extractors/extractors.go: 5 classes, 25 functions; imports appconfig.go, client/errors.go, internal/ctxlocal/ctxlocal.go, internal/headerlookup/headerlookup.go

internal/headerlist/headerlist.go: 14 functions

internal/headerlookup/headerlookup.go: 7 functions; imports appconfig.go, internal/fieldname/fieldname.go

internal/memory/memory.go: 2 classes, 9 functions

internal/fieldname/fieldname.go: 2 classes, 11 functions

middleware/logger/logger.go: 4 functions

app.go: 9 classes, 61 functions; imports binder/binder.go, binder/json.go, binder/xml.go, client/errors.go, internal/nilerror/nilerror.go, log/context.go, log/log.go

binder/xml.go: 1 class, 2 functions

internal/etag/etag.go: 5 functions; imports internal/headerlist/headerlist.go

internal/mediatype/mediatype.go: 8 functions

appconfig.go: 1 function; imports internal/appconfig/appconfig.go

internal/clocktest/clocktest.go: 1 function

internal/ctxlocal/ctxlocal.go: 1 function

internal/loggertest/loggertest.go: 1 function; imports log/log.go

internal/redact/redact.go: 1 function

middleware/logger/errors.go: 1 class, 2 functions; imports client/errors.go, internal/logtemplate/errors.go

path.go: 6 classes, 43 functions; imports internal/paramdelim/paramdelim.go

binder/binder.go: 2 functions; imports client/errors.go

binder/cookie.go: 1 class, 2 functions

internal/quotedstring/quotedstring.go: 2 functions; imports internal/bytepolicy/bytepolicy.go

middleware/session/session.go: 1 class, 31 functions; imports binder/cookie.go, extractors/extractors.go, log/context.go

internal/bytepolicy/bytepolicy.go: 6 functions

internal/logtemplate/errors.go: 1 class, 1 function; imports client/errors.go, middleware/logger/errors.go

internal/nilerror/nilerror.go: 1 function

internal/paramdelim/paramdelim.go: 1 function

internal/schemehost/schemehost.go: 6 functions

internal/urlnorm/urlnorm.go: 4 functions

internal/wiretarget/wiretarget.go: 14 functions; imports appconfig.go

middleware/recover/recover.go: 3 functions

prefork.go: 4 functions; imports app.go, internal/tlstest/tls.go

internal/byterange/byterange.go: 1 class, 8 functions

internal/contextvalue/contextvalue.go: 3 classes, 1 function; imports log/context.go

internal/crosshost/crosshost.go: no top-level classes or functions

internal/fspath/fspath.go: 9 functions; imports path.go

internal/idnafold/idnafold.go: 1 function

374 further files are in the graph but not listed here.Files that import each other

client/errors.go and internal/logtemplate/errors.go

internal/contextvalue/contextvalue.go and log/context.go

NeedyNodes is a free, browser-based tool that turns a codebase into an interactive dependency map: folders become regions, files are laid out in the direction their imports run, and circular dependencies or dead exports are flagged automatically. Point at a file to see what it uses and what uses it, or double click it to see every file a change to it can reach. It parses JavaScript, TypeScript, Python, Go, Rust, Vue and Svelte, up to 1000 files per map. Nothing is uploaded: parsing runs entirely in the browser.Browse all visualized codebases · Visualize your own codebase