You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 10, 2022. It is now read-only.
I'm trying to use the import ... from @wordpress/... syntax. Writing import domReady from @wordpress/dom-ready should build successfully, and it should refer to wp.domReady.
Actual Behavior
I receive the "module not found" error. .
I think this is very easy to fix by adding "dom-ready" here:
I think @wordpress/compose also presents the same issue. @ahmadawais would it be possible to make it so that when something is imported from @wordpress/whatever, it is accessed as wp[camelCaseDash(whatever)]?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug Report
Expected Behavior
I'm trying to use the
import ... from @wordpress/...
syntax. Writingimport domReady from @wordpress/dom-ready
should build successfully, and it should refer towp.domReady
.Actual Behavior
I receive the "module not found" error.
.
I think this is very easy to fix by adding "dom-ready" here:
create-guten-block/packages/cgb-scripts/config/externals.js
Line 20 in bdc4019
The text was updated successfully, but these errors were encountered: