feat: support CSP by adding optional nonce #2501
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Why
Related Issues:
Changes
RainbowKitProvider
now accepts an optionalnonce?: string
.get-nonce
library (See: Violates safe CSPs because of dependency applying style tags theKashey/react-remove-scroll#21).Usage
You can now optionally pass a nonce prop to RainbowKitProvider:
Note
The nonce must be generated per HTTP response by your server (do not hard-code).
See Next.js CSP guide for an example.
PR-Codex overview
This PR introduces support for Content Security Policy (CSP) by adding an optional
nonce
parameter to various modal components in therainbowkit
package, enhancing security for inline styles.Detailed summary
package.json
to includeget-nonce
dependency.nonce
prop toAccountModal
,ChainModal
,RainbowKitProvider
,ModalProvider
,Dialog
, andConnectModal
.setNonce
function fromget-nonce
inDialog
component.