I've been trying to convert my website into a project with Tauri for the past 3 days and I'm not getting any intended results even though I followed the tutorial on Tauri Documentation countless times.
When I run npm create tauri-app to create a starting template for my project, I should be able to get a result like the following.
https://www.freecodecamp.org/news/content/images/2022/10/Screenshot-from-2022-10-11-14-03-45.png
(Copyrights go to relevant authors)
But I always get something like this.
My build
After I got this problem I emptied my project folder, uninstalled npm and tauri-cli reinstalled it again, and followed the tutorial but still get no good results. I continued the same procedure more than ten times in a row. I also tried using other package managers which were available but didn't work for me.
Then I checked the src file within my project folder which contained the related html, css and javascript files for the demo and opened index.html. It also looked like this.
Demo HTML files viewed through a browser
Browser console had following issues and I have no idea what's going with my Tauri project all the time.
Issues in the browser console
I swifted through the official Tauri GitHub resp and found no any issue like this is filed by somebody. I really apprciate if any possible solution is given regarding this issue.
Tauri CLI: #tauri-apps/cli#1.2.2
OS: Windows 11 Home Single Langauge 10.0.22623 Build 22623
Both npm and Node.js are up-to-date.
Related
I am very new to web development and I am starting my first project using frontendmentor.io. I began my project Monday and everything was working fine. All of a sudden on Tuesday, I began to get a error message when trying to open live server.
The error message reads:
Error: ENOTDIR: not a directory, stat '/Users/username/html/index.html/'
I have searched plenty of forums and cannot really find anything that fits my situation. I am using only HTML and CSS for this project. I uninstalled VSCode and I lost all of my previous work, so I only have the code that frontendmentor provided to get started, but I can post that below if needed. I am sure I did something wrong, I just cannot figure out what exactly.
I had that problem too.
I opened the CSS file with live server instead of index.html file and it works.
Please forgive my ignorance, Any advice/directional assistance would be greatly appreciated.
I have a small app that reads data from an API with json requests.
One of the actions the app needs to do is to download a given PDF and open it either in the app, or in the OS default viewer.
I have followed several guides, but I think I am not including all needed files or something. The guides don't speak of including files of any type, but I still get errors.
In this link for example I followed the steps, but I am getting an error when I add these two lines in to the script at the bottom of the page:
var fileTransfer = new FileTransfer();
console.log(FileTransfer);
When running that I get the error Uncaught ReferenceError: FileTransfer is not defined at employee_documents.html:102
I am sure that either i am not including the files correctly in netbeans or I am missing something simple...
Any advise would be greatly appreciated.
To answer the question specifically. In order to solve the error, you need to run the cordova app using the CLI. In that way, the plugins installed from your cordova will be used otherwise if you're only running it via refresh or something similar it will produce an error like this.
In other words, type this command in your CLI:
cordova run browser
You can change this to your preferred platform (android, ios)
I'm having problems running the polymer build command of the polymer CLI, it gives me the following feedback:
and neither of my built folders (bundled or unbundled) have the javascript files. The build process places <script> tag with the src of a javascript file in the place of my javascript code, but this files are not being generated.
I don't know if both errors are related, but I don't know what can I do to generate the <component>.html_script_0.js files.
I had this same problem and saw that there were several issues reporting it.
It seems a fix has been already merged and is part of v0.9.0 but I'm not completely sure if the fix is up on npm just yet.
All files seems to have run through the build script without any problems except my HTML files. They get added to my publish folder but are completely empty. I have tried both ant build and ant minify.
If i comment out this line file.pages.default.include = index.html, 404.html the files don't get emptied.
One more weird thing happend to. My generated css version started at around 40 the first time i ran the script. Doesn't matter at all really. Just a bit odd.
Update:
I noticed i get this error. ERROR: For JavaScript or CSS compression YUI compressor jar file must be present in the same directory as HtmlCompressor jar.
Read a thread where Paul Irish was saying that updating to the latest htmlcompressor jar should solve it. I did that but some reference somewhere needs to be updated with the new filename to cause now i get an error saying that the htmlcompressor jar couldn't be found.
For those who have the same issue, this has just been answered at the mobile boilerplate site: https://github.com/shichuan/mobile-html5-boilerplate/issues/46
plz anyone can tell me how to open our project at Appmobi XDK. i am facing a problem that i have install it but its not allow me to open projects. when i tried to open my project a message comes unable to open a project.
now i need your help guys.
Thanks
The very first thing you need to do is to go to xdk.appmobi.com (in google chrome) and download/install our xdk. (Need Java installed also)
During the install you will need to set a default appmobi directory. This is where your app files will be stored.
Create a new app from within the XDK. You can then click the edit the source code button in the tool bar to edit your code. Here you can update the file with your own code.
You can check out a video that explains the xdk at http://www.youtube.com/watch?v=MWV8kOJlGmc Some things might have changed visually with the current version of the XDK, but essentially its the same.
Some things have changed/moved around the screen since we made the video, but essentially its functionally the same.
Check it out as it will give you tips/how To's to using the XDK.
Also, posting in our forums (forums.appmobi.com) will get your questions answered sooner!