HTML5 Export Errors - lsqlite3

bigtunacan

I have an existing working application that I tried using the HTML5 export for the first time and am getting a couple of different errors.

The first is trying to use sqlite3; once I try to load sqlite

sqlite3 = require('lsqlite3')

The application crashed due to not being able to find the lsqlite3 plugin.

lsqlite3.lua Not found in archive lsqlite3.so Not found in archive *visit(TouchEvent* v)* stack NOT ok begin:0 end:7 delta:0 *CppLuaBridge::luaEvent* stack NOT ok begin:0 end:7 delta:0 *enterFrame* stack NOT ok begin:0 end:7 delta:0 scenes/SelectScene.lua:34: module 'lsqlite3' not found: no field package.preload['lsqlite3'] no file './lsqlite3.lua' no file '/usr/local/share/lua/5.1/lsqlite3.lua' no file '/usr/local/share/lua/5.1/lsqlite3/init.lua' no file '/usr/local/lib/lua/5.1/lsqlite3.lua' no file '/usr/local/lib/lua/5.1/lsqlite3/init.lua' no file './lsqlite3.so' no file '/usr/local/lib/lua/5.1/lsqlite3.so' no file '/usr/local/lib/lua/5.1/loadall.so'

The second issue is that any page loads correctly the first time (not using sqlite in this case), but then errors out on subsequent loads; this also seems to be tied to a library/plugin not being able to load however.

Sync FS lfs.lua Not found in archive lfs.so Not found in archive *callFile* stack NOT ok begin:1 end:7 delta:-1 utils/run_migrations.lua:2: module 'lfs' not found: no field package.preload['lfs'] no file './lfs.lua' no file '/usr/local/share/lua/5.1/lfs.lua' no file '/usr/local/share/lua/5.1/lfs/init.lua' no file '/usr/local/lib/lua/5.1/lfs.lua' no file '/usr/local/lib/lua/5.1/lfs/init.lua' no file './lfs.so' no file '/usr/local/lib/lua/5.1/lfs.so' no file '/usr/local/lib/lua/5.1/loadall.so' stack traceback: utils/run_migrations.lua:2: in main chunk main.lua:34: in main chunk

hgy29

Yes, only bitop, json and luasocket plugins have been ported currently (beside Facebook and Ads plugins which are available to KS backers only).
SQLlite should be straightforward to port though, and lfs shouldn't be problematic either.

antix

Unless you actually require the features of a database, I would recommend JSON, it's pretty flexible.