I did fire up web inspector (Safari) and there it shows:
TypeError: undefined is not an object (evaluating 'n.$el.append')
This vite.config.js thing is someting nobody understands.
@deejay how can I check that? The official documentaiton is very small.
And how can I propperly install V6? I prefere locally, within the project directory, so that it does not get mixed up with other projects.
How can I install using NXP (new this is integrated with npm but how to call nxp within npm?)
No where is a full installation instruction set.
% framework7 create --ui
All good, you have latest framework7-cli version.
Framework7 project already set up in current directory
Ok, but then it’s broken. I did a new project with vite and FONTS are missing, it places it in the wrong directory, etc. is this normal? Without vite package thing also.
(As if I remember right this is BROKEN since version 3? Why these things don’t get fixed?)
Can I DISALBE vite compression temporarly within vite settings just for debuggin my app? How?
The question also was HOW can I add my own assets files like local json files and .js with this vite thing? It does not get deployied with
npm run build
npm run build-cordova-ios
So then files are missing and sure will and can not work then.
Thank you very much for your information I will get into that.
Missing fonts problem
I found out that this does not work does not get executed? I can call it manually but then it does not copy the fonts. (As far as I can tell this never worked since 3.x don’t know why. I also needed to copy them manually back then.)
Fonts not copyied to the right place - Solution found / FIX / macOS
It’s getting executed but it does NOT copy the files (fonts). I can run it manually but nothing happens. So, it’s broken… don’t know why. (macOS. Windows not tested.)
I have to do it (copy files) manally to put them in ./src/fonts folder. (The npm, bundler, things does not work here. Maybe on Windows but not on macOS)
How to debug=?
So the problem is with cpy. cpy on a macOS DOES NOT copy the files within the given target directory instead it will take the source directory structure with it. Which is wrong in this case.