I called my project ink.ink, and later went to export it to the web. Inky made a file called ink.js that corresponded to my story's json, which overwrote the ink.js that is the Inkjs engine used for running Ink on the web. There was no error message for overwriting, my web export simply had an error.
I suggest: when the user tries to export their project and it's called either main.ink or ink.ink, Inky should give a helpful error message: "Cannot export projects called 'ink.ink' or 'main.ink' for the web. Please rename your project and try again." and refuse to export. This would prevent headaches for the end user.
I called my project
ink.ink, and later went to export it to the web. Inky made a file calledink.jsthat corresponded to my story's json, which overwrote theink.jsthat is the Inkjs engine used for running Ink on the web. There was no error message for overwriting, my web export simply had an error.I suggest: when the user tries to export their project and it's called either
main.inkorink.ink, Inky should give a helpful error message:"Cannot export projects called 'ink.ink' or 'main.ink' for the web. Please rename your project and try again."and refuse to export. This would prevent headaches for the end user.