Sandbox #1004
-
Hey Alloy community, I started the sandbox project locally and trying to navigate it to see how it works. When I reload the home route, I don't see the console log "Alloy Instance Created" or "Alloy Instance Configured", also clicking on "Get ECID" doesn't send any request and no callback invoked. Would love to hear your thoughts how to get this sandbox to a working state. It took some digging to realize that http://localhost:3000/alloy.js file is missing? when I try to load the file the app home loads. Is this the recommended pattern to load Alloy into a react project? We are looking to migrate this to our new MFE architecture, and I was thinking we can load this on the shell so all the micro apps can have alloy methods available on the window. This would give us easier process to release updates etc. How come npm install of Alloy wasn't used in the Sandbox example? DS |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Are you running the sandbox from the root directory of the repo with
Because we want to use the sandbox to test in-progress changes to alloy, so we want to use the built version of local code instead of the production version.
No. Follow the documentation: https://experienceleague.adobe.com/docs/experience-platform/edge/fundamentals/installing-the-sdk.html?lang=en |
Beta Was this translation helpful? Give feedback.
Are you running the sandbox from the root directory of the repo with
npm run dev
, or are you running it from inside thesandbox/
directory?If you run it from inside the
sandbox/
directory, Alloy is not built.Because we want to use the sandbox to test in-progress changes to alloy, so we want to use the built version of local code instead of the production version.
No. Follow the documentation: https://experienceleague.adobe.com/docs/experience-platform/edge/fundamentals/installing-the-sdk.html?lang=en