I need to work on an existing Big Commerce site.
I've downloaded and installed Stencil CLI with no issues.
I've logged into my BigCommerce site and set up a Stencil API Token, I've downloaded the theme, extracted it and run npm install. I then ran:
stencil init --url https://yourstore.com/ --token 19d3ae6-dc15-4af9-bead-a2c703aa7b --port 3000
with no issues. Then ran stencil start.
However, I get the error:
not ok -- Error: The BigCommerce Store you are pointing to either does
not exist or is not available at this time. Error details: Request
failed with status code 404
I've tried both my store's URL and https://store-12345.mybigcommerce.com/ and ensured there was a / at the end of the url.
The site loads fine - I can access the front end without issue.
I've running version 3.2.1 of Stencil and version 12.18.3 of node.
Would anyone know what I should be doing?
As a workaround, this may help -- it suggests disabling ssl checks and since the cli is only used for dev purposes this isn't a dangerous decision. :)
Related
My NPM install step is configured to use registries in .npmrc,
My .npmrc is as follows
registry=https://pkgs.dev.azure.com/xxx/xxxx-xxxx-xxxx/_packaging/design-system/npm/registry/
always-auth=true
The Azure Artifacts feed is set-up, and a local npm install from my dev machine works completely fine.
However the pipeline's npm install job always fails with error 403.
What am I doing wrong here? I've also tried changing the npm install task to use Registry I select here, and linking it to my "design-system" feed directly, but it results in the same error. I've followed all the steps here https://learn.microsoft.com/en-us/azure/devops/artifacts/npm/npmrc?view=azure-devops&tabs=windows, but it just doesn't work. Thanks
Problem solved. What I had to do was go under into the feed -> settings -> permissions, and add the ...Build Service... as a Contributor.
Microsoft should really add this as part of their documentation. Took me several hours of random attempts before I found it..
This is a different solution for the same message, although, in this case it will fail from any location.
Trying to publish a package version previous to the last one published on the feed will return the 403 Forbidden error to, even if it's not a permissions issue.
Updating the package version to one increment after the current version will solve the problem.
I'm trying to set up swagger-editor locally.
After cloning, I ran it using npm start but it never works on the browser .
and the browser gives the error:
This page isn’t working localhost sent an invalid response.
ERR_INVALID_REDIRECT
My nodejs version is 10.16.1 and npm version is 6.9.0.
Does it work only with 6.x version of nodejs? Did I miss anything here?
Or is there any other tool for setting up swagger-editor locally or using it?
Thanks.
I'm kinda new to strapi. actually this the first time to try it. so i followed the documentation and was able to get the first page to work but admin page always go blank. sadly i don't know nodeJs or react so I'm not sure about what to do in here but seems there's something wrong with the permissions please check the attached image.
i've tried
npm install in the project root directory.
npm run setup in the project root directory.
as mentioned in this issue on github but it want's useful
I'm using
strapi 3 alpha
nodeJs 11
npm 6+
mariaDB 10.1
windows 10 64bit
I suggest you to clean the database your use. And when it's done, restart your Strapi server. It will re-create all table needed by Strapi.
So simply, I checked strapi website to find out that version 3 is out of the alpha status and then I installed the newer version and tried to use it and it did work so seems some bug was in the alpha edition which strapi team has fixed by themselves
I had a similar issue after setting up SSL on Digital Ocean one-click. I just ran npm run build. I did not do anything with the database.
I'm trying to deploy my node.js sails app on openshift. I followed procedure outlined in https://gist.github.com/mdunisch/4a56bdf972c2f708ccc6 but still doesn't work.
also try this: Node.js app on openshift
no matter what i'm getting "Service Temporarily Unavailable"
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. Error.
Hopefully someone can at least point me to the right direction.
Thanks in advance.
I have also deployed my application onto openshift and here are my steps
Create a node.js Cartridges 0.10
In the repo, please mention "https://github.com/ryanj/nodejs-custom-version-openshift" since my sails need npm version 1.4.0 and the original one is 1.3.X
git clone the repo
copy your file into that repo
Follow this page https://gist.github.com/mdunisch/4a56bdf972c2f708ccc6
The first two steps should be done if you haven't changed the original stuff. The only things is to change ".openshift/action_hooks/pre_start_nodejs" and append that at the end to make it is as a production and run the grunt
git add . and git push
It will automatically build and at the end will tell you deployment completed with status: success
I am also new but hope you can try. Thanks
One more things, if missing the step 5, you won't run the sails and can't see the log in the terminal and result in 503 on browser.
But I have another question after each push on openshift, you can see my log if you want to know what is the right status
Why mongodb is reset after push to openshift
Another suggestion is to ssh and make sure the npm -v is larger than 1.4.0, try to npm install -g npm to update the version.
If still fails, i will suggest to npm install sails -g and try to commit and look for the build..
I am trying to test es-6 promise-polyfill, for the testing one the node packages requried is broccoli-closure-compiler, which is not getting installed, I am behind a proxy server, is that the problem, but i have proxy config for both git and npm, so they are working fine, for more info, please refer to the screenshot of the command prompt,
edit:
the text in screenshot
D:\pt>npm install broccoli-closure-compiler
npm WARN package.json jshint#0.9.1 No repository field.
\
closurecompiler#1.3.2 install D:\pt\node_modules\broccoli-closure-compiler\node_modules\closurecompiler
npm run-script configure
\
closurecompiler#1.3.2 configure D:\pt\node_modules\broccoli-closure-compiler\node_modules\closurecompiler
node scripts/configure.js
Configuring ClosureCompiler.js 1.3.2 ...
Downloading http://dl.google.com/closure-compiler/compiler-latest.tar.gz ...
? Download failed: Error: connect ETIMEDOUT
? Unfortunately, ClosureCompiler.js could not be configured.
See: https://github.com/dcodeIO/ClosureCompiler.js (create an issue maybe)
what I am suggesting is not a solution, these are mere work-around( aka really bad hacks)
if you are facing this, it is because you are behind a proxy server and one of the scripts trying to install clousurecompiler does not have the proxy settings set.
work around one : well, find a way to connect without proxy server, or install in a machine outside proxy server, copy the node_module files to your system,
work around 2 (the one I used) :
when you look at the screenshot, you would notice that at one point "node scripts/configure.js" is run, this is the crucial point, find a way to pause the processing just before this point,
open the 'configure.js' file, it would be at '.\node_modules\broccoli-closure-compiler\node_modules\closurecompiler\scripts' in node project directory,
comment line 65 in that i.e fail(); to //fail();
continue the installation process,
manually download http://dl.google.com/closure-compiler/compiler-latest.tar.gz , put the extracted file at '.\node_modules\broccoli-closure-compiler\node_modules\closurecompiler\compiler' in your project directory
(... told you this is a bad solution )