egutierrez
9661a5ce1f
The SPA (web/) and the web gateway (cmd/webgw) move to a dedicated app projects/message_bus/apps/uniweb (its own Gitea sub-repo). unibus is now strictly the bus plane: membership/keys, the client library and demo peers. uniweb consumes unibus as a Go module via replace => ../unibus. No capability lost; same SPA and gateway, in their own service folder. go build/vet/test green after extraction.
get-nonce
just returns a nonce (number used once). No batteries included in those 46 bytes of this library.
- ✅ build in
webpacksupport via__webpack_nonce__
API
getNonce(): string|undefined- returns the currentnoncesetNonce(newValue)- set's nonce value
Why?
Why we need a library to access __webpack_nonce__? Abstractions!
"I", as a library author, don't want to "predict" the platform "you" going to use.
"I", as well, want an easier way to test and control nonce value.
Like - nonce is supported out of the box only by webpack, what you are going to do?
This is why this "man-in-the-middle" was created.
Yep, think about left-pad :)
Webpack
To activate the feature set a webpack_nonce variable needs to be included in your entry script.
__webpack_nonce__ = uuid(); // for example
Without webpack __webpack_nonce__ is actually just a global variable,
which makes it actually bundler independent,
however "other bundlers" are able to replicate it only setting it as a global variable
(as here in tests) which violates a "secure" nature of nonce.
get-nonce is not global.
Used in
react-style-singleton<-react-remove-scroll<-react-focus-on
Inspiration
Licence
MIT