We could consider making the header information configurable, so you basically register a key (String) and a value transformer (some protocol). The package then comes out of the box with configurations for the current setup.

Add a reminder/gotcha/heading that in case you are using meta in a project that would serve files from directories not listed in the exceptPaths array you would have to add these.

When attempting to create a new NMeta struct as an extension on a Request this sanity check exists

guard components.count == 5 else {
    throw NMetaError.invalidHeaderFormat
}

This works fine for the native platforms but for a request from a web platform the last three parts can be extracted from the User-Agent as described in the README

For web platform only platform and environment is required, since the rest can be found in User-Agent.

Therefore, we need to extend the checking to consider web and then extract what can be extracted from the User-Agent if the platform is web before we throws errors

Change Application.NMeta.platforms, .environments, .requiredEnvironments to by of type Set to speed up checks.

As the title says loading javascript-, css- and image-files from the public folder fails because it expects an N-Meta header in the request.

We need to bypass the header check if the request concerns ressources from the public folder.