You can just import your project from GtiHub again. It’ll overwrite all of the files in the Glitch project currently, leaving you with just the latest versions from the GitHub repo.
Does it consistently do that when trying to import? If so, let us know if there are any other errors that you see in the browser dev console when the import fails. Thanks.
abort: function abort()
always: function always()
catch: function catch()
done: function add()
fail: function add()
getAllResponseHeaders: function getAllResponseHeaders()
getResponseHeader: function getResponseHeader()
overrideMimeType: function overrideMimeType()
pipe: function pipe()
progress: function add()
promise: function promise()
readyState: 4
responseJSON: "error importing into project <project-id>"
responseText: "\"error importing into project <project-id>\"\r\n"
setRequestHeader: function setRequestHeader()
state: function state()
status: 500
statusCode: function statusCode()
statusText: "Internal Server Error"
then: function then()
__proto__: Object { … }
it looks like package.json specifies some commit-related hooks which fail when you try to import again from GitHub. We opened a bug report to fix this issue, but in the meantime, you can get up and running by removing these scripts from package.json: commit, precommit, commitmsg.
Moreover, it looks like some script is trying to modify programmatically the content of package.json: currently, we don’t support out-of-editor interaction with an editable file, so I would suggest you to use the terminal (Project menu -> Advanced Options -> Open Console) to edit package.json.
Sorry for the inconvenience, I’ll keep you posted when we figure out how to handle commit-related scripts in package.json!
I appreciate that you identify the problem and suggest the solution but it seems not to be realistic. I will recreate project every time until this issue will be solved.