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
ReactRouterDOM =require('react-router-dom'); // react-router DOM interface
373
+
ReactRailsUJS =require('react_ujs'); // interface to react-rails
373
374
// to add additional NPM packages call run yarn add package-name@version
374
375
// then add the require here.
375
376
```
@@ -406,15 +407,16 @@ end
406
407
407
408
#### Manage the Hyperstack dependencies with yarn
408
409
409
-
As you can see above the NPM modules that Hyperstack depends on are part of the webpacker manifests.
410
-
But by default Hyperstack will pull copies of these packages into the old-school Rails sprockets asset pipeline.
411
-
So if you are using Webpacker you need to add the packages using yarn, and then tell Hyperstack not to
412
-
include them in the sprockets asset pipeline.
410
+
The above changes will pull the necessary NPM modules in as part of the webpacker manifests.
411
+
But by default Hyperstack will try to pull copies of these packages from the Hyperstack gem set using the old-school Rails sprockets asset pipeline.
412
+
413
+
So instead, when using webpacker, you need to add the packages using the `yarn` package manager, and then tell Hyperstack not to include them in the sprockets asset pipeline.
413
414
414
415
To add the packages using yarn run these commands:
0 commit comments