It's less of a framework, and more of an asynchronous module loader, but what that gives you is:
A schema within which you can define, load, and reuse self-contained modules w/o all the NPM fluff and packaging
A browser-native module loader that makes it easy to re-use other packages (even NPM builds) by wrapping them in a define() closure
A very nice way to structure and organize your JS projects in a Python-like mapping of modules-are-files logic
Oooh! Almost forgot:
You also get loader extensions for defining manual (and asynchronous) loading logic for "special" resources that aren't pure JS, like JSX (or even ZIP, CSV, and others)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I would strongly recommend RequireJS.
requirejs.org/
It's less of a framework, and more of an asynchronous module loader, but what that gives you is:
A schema within which you can define, load, and reuse self-contained modules w/o all the NPM fluff and packaging
A browser-native module loader that makes it easy to re-use other packages (even NPM builds) by wrapping them in a define() closure
A very nice way to structure and organize your JS projects in a Python-like mapping of modules-are-files logic
Oooh! Almost forgot: