checkout hangs on Stencil theme - bigcommerce

We are in the process of developing a theme for a client using Stencil. On our local development the checkout.php just hangs. Cart loads fine but just sits there moving to the checkout. Should it be possible to complete checkout thru our local development? Are there special configurations that have to be made?

Related

How to get hot reloading working with React.js project template in VS2022 Mac

I am using the React.js project template in VS2022 for Mac and the application starts up fine when run with “Start Debugging” or “Start Without Debugging”. When making changes to the React front end code, the page refreshes and the changes are instantly viewable. However, when making any changes to the backend API code, you have to stop and restart in Visual Studio before the changes are reflected in the API calls.
I have also tried running the application with “dotnet watch” from the terminal and in this case I can see the API being re-compiled in the output window when a change is made to the API code, but then it seems to kill the dev proxy server because I am not able to refresh the page as it just returns “The site can’t be reached” (I can see the bash process getting killed in activity monitor, which I think is hosting the dev proxy server). I have to restart the application again in Visual Studio to get it working and see the changes to the API code.
Is there a way when using the SPA proxy in VS 2022 so that you can make changes to either the front end or back end code and have those changes hot reloaded?

What's the best way to do end to end testing that can be run via CI pipeline when the frontend and backend are in separate repos?

I currently have an Angular frontend and a dockerized Django backend. Both are deployed separately. Angular via Netlify and Django via Heroku. Both are triggered to deploy any publishes to the master branch.
I've written end to end tests using Cypress and integrated it to the CI using GitHub actions. At the moment I ended up deploying a test backend server which is a replica of the production on a separate Heroku instance and am using that link as the backend for the cypress test suite that lives inside the UI repo and runs every time before pushing to master. To be more specific, whenever I need to publish changes, I push to staging and on push to staging, the CI workflow is triggered and runs the test and if the tests pass, the changes to staging get merged with master and from there changes are automatically deployed. The backend gets published to production without any prior testing.
There are two problems with this setup. First is that for the CI to rely on an external API is time consuming. Second thing is that for me to push changes to the API without the e2e suite running and having it only be run when corresponding UI changes get published is sort of problematic because breaking changes to the API could get published unchecked.
Is there a more elegant way to do this within GitHub actions? Because I find it convenient. If not, what other solution do I have to address these 2 issues?

Shopify Backup Changes Routed to Hosted Domain GoDaddy

I am currently making changes in a live shop. So I have duplicated my live theme and am making changes in my duplicate. 
Still all my changes are visible in my live website. Somehow, all my themes in my shop are routed to my hosted domain at GoDaddy. 
Does anyone have an idea how I can prevent this from happening and can only route my live theme to GoDaddy? 
Kind regards
Let's call the duplicate theme dev and the live one live. They are all hosted on the same domain from GoDaddy
This should be the way to modify dev vs live environment, by using theme kit and use git to track files
3 Simple Steps for Setting Up a Local Shopify Theme Development Environment
Live Reloading Shopify Themes: Sass Compilation with Theme Kit and Prepros
Base on the information you gave, I will check the following
-check that you are not previewing the dev theme.
-check that when you are editing the correct theme.
-make sure to only edit files offline. This will save you so much trouble.

How to create a shopify app dev environment

I'm building an embedded shopify app and I struggle to test it as embedded app because it's veeeery slow. I started my app following the official guide of creating an app with node & nextjs and I'm still using both but i'm considering getting rid of nextjs and using just react since it feels veeery slow and so heavy for ngrok to transfer all the files to the shopify iframe...
What would you recommend to work smoothly with shopify when building an embedded app?
(I'm mostly working locally but I still need to often go check that it works well inside the admin & to use shopify-app-bridge library)
if ngrok is slow for you, i would suggest heroku for deployment and testing,
create new application at heroku, you can also connect it with your github and use automatic deploy when you push your code

How to make dojo work offline

I have a project that loads http://ajax.googleapis.com/ajax/libs/dojo/1.3.2/dojo/dojo.xd.js, I want to be able use this project offline
I tried to download dojo.xd.js and link to it locally but this still doesn't work offline
In firebug, on the net tab I can see that there are a lot more .js files that load
Is there a simple way of making this work offline?
The way of integration depends on your way of using it.
I assume you have webserver running locally (without inet access)?!
At the dojo website there are several ways of dojo integration available. Just download one of them (do not use CDN) and put the file on your local web server. Then it is available through the local url (can be relative to your site).
If you wan't to build an "offline" app without a webserver then take a look at Adobe AIR and interation of the dojo toolkit with Dojo Extensions for Adobe AIR.
Another option might be the integration together with PhoneGap or Cordova to build an offline App, e.g. for an IPhone etc. with HTML/Javascript. Win8/RT Applications for the M$ AppStore does support HTML/Javascript, too (have not tested this with Dojo).
Keep in mind there are also some security restrictions (e.g. loading and execution of JavaScript) if you plan to "release" your app as simple html file (click to open in browser).