
1·
4 hours agoWonderful day!
The actual script file is minified. And we may see the actual position the error points to: 2:1170023.
That is the second line and 1170023 character on that line. If we check it out manually, we may see the following, from 1169975 to 1170025 character positions:
(r.state=u({},r.state,{form:u({},r.state.form,d)}))
hw mentioned in the error is probably the following function:
function hw(e,t){var n;t.target?(t.preventDefault(),n=t.target.files[0]):n=t,e.setState({imageLoading:!0}),Ln.client.uploadImage({image:n}).then((function(t){"success"===t.state?"ok"===t.data.msg?(e.state.form.url=t.data.url,e.setState({imageLoading:!1,imageDeleteUrl:t.data.delete_url})):"too_large"===t.data.msg?bo(po.i18n.t("upload_too_large"),"danger"):bo(JSON.stringify(t),"danger"):"failed"===t.state&&(console.error(t.err.name),bo(t.err.name,"danger"),e.setState({imageLoading:!1}))}))}
Yet, these two are valid in terms of JavaScript syntax.
Meanwhile, DeepSeek states utter nonsense. The space is not required in JavaScript declarations. You may check it yourself:
var e,t,n=1,r,o=2; console.log({e,t,n,r,o});
// {e: undefined, t: undefined, n: 1, r: undefined, o: 2}
I would start by deploying non-minified scripts, and with the error/exception thown, set breakpoint in the previous stacktrace step. Then, reload/repeat, and follow the logic step by step until the exception stage.