remove < IE11 compatibility from /demand/weakmap

7.0.4

remove < IE11 compatibility from /demand/weakmap

UMD-support for handler/module

The default handler is now able to handle standard UMD-modules in addition to demands proprietary module defintion. As this may cause compatibility issues (as probably most of the modules that previously required to be loaded via legacy-handler area UMD actually) it is currently hidden behind the following config setting and defaults to false:

'/demand/handler/module': {
  umd: true
}

7.0.2

fix provide being able to handle empty dependency array

re-add legacy scripts resolving to true when no probe is defined

7.0.1

fix bug where legacy handler did not resolve with true when probe was…

breaking change to path-resolution

• switch path resolution to assume absolute if not guaranteed to be relative (opposite before)
• remove async probe from legacy handler as it was not working as expected
• fix sourcemap path resolution which had some minor issues

cleanup & minor genie improvement

• allow RegExp in genie patterns
• remove obsolete escapeRegex function

make legacy probe optional and fix resolving sourcemap URLs

• make legacy modules always resove with true if no probe is defined
• treat URLs without file-suffix as directories when resolving sourcemaps

make provide compatible to rollup amd/umd modules from npm monorepo

• fix demand attaching a write protected "define" method to Object.prototype making it impossible to reach full AMD compatibility
• modules starting with an "@" are now treated as absolute paths and can therefore be handled via pattern
• stop attaching ".js" when module starts with an "@"
• when a module depends on "exports" (which rollup umd/amd packages do) provide an object and resolve the dependency itself with this object

fix bug in /handler/json

6.0.2

fix bug in /handler/json

add unhandled-rejection handling to /demand/pledge

6.0.1

finalize changes to /demand/pledge