I have an SPFx web part which contains TinyMCE self-hosted component. The webpart's editor component in RichEditor.tsx file returns node with 'tinymceScriptSrc' property. The tinymceScriptSrc has value to tinymce.min.js file.
This works as expected while executing in workbench but does not turn up in packaged solution.
Executed gulp serve command and the webpart shows TinyMCE component in workbench.aspx. However, it does not appear in a webpart from packaged solution.
Related
I want to publish my Svelte web app to GitHub pages and based my application on the template https://github.com/sveltejs/template. When I run npm run build, public/build/bundle.js is created but no index.html. All the tutorials I found talk about how to deploy Sapper projects, or to use external tools like Vercel and Surge, but is it possible to just build Svelte without any external tools? All I want is a static HTML page that I can copy to GitHub pages.
Edit: See the accepted answer for the general approach, however for non-root-directory-deployment, you still need to make the paths relative. I created a pull request at https://github.com/sveltejs/template/pull/239.
In svelte, index.html is a static file which will import your bundle.js and run it.
index.html is located at /public/index.html while your bundle.js is located at /public/build/bundle.js
in svelte template, index.html imports /build/bundle.js using a script tag to initialize the application.
while deploying, you just need to upload the whole /public folder and everything should be operational.
I have downloaded the QAF Maven project and imported into Eclipse. I have created BDD test case for one of the RESTFull service and I am able to run it as TestNG Test. I see the result folder created with the date and timestamp created under test-results folder. When I try to refresh the Dashboard.html I don't see any results and it’s empty.
Please let me know if I have to update my POM or any other property file.
Try opening dashboard.htm in firefox.
You need to open local dashboard.htm in Firfox (prefered), Edge or Safari. If you are opening in chrome you need to set allow file access from file. If dashboard.htm served through http server, for example jenkins then you can open in any browser.
I'm trying to learn Vue.js as well so I create a simple folder called VueTest.
I have two files in the folder:
app.js
index.html
I found the info on how to configure the task runner to open up the current file and I have that setup to open in Chrome, which it does. However, because it's not running as a project, my index.html doesn't see the app.js file and so my Vue project is not working correctly. I just runs the HTML code an all I see is my mustache code (ex: {{Title}}).
How do I run files as a project?
If get it correct - you want to launch js app without opening teminals outside 'VS Code' then you have to see this
Have fun
I found my mistake, it's actually easy and I should have figured this out before posting.
To run Index.html on it's own, all I had to do was make a script reference in the page pointing to the app.js file. I didn't have to do that in JsFiddle.
you can't run files as a project in VS Code. it is just a text editor.
I'm learning Aurelia via the TypeScript / ASP.NET Core skeleton navigation app. Everything runs fine in its default state. To test the exported production bundle, I run the Gulp Export task, then publish the app via Visual Studio project publish to a local folder, then replace the published wwwroot folder with the wwwroot folder from within the "export" folder, then use dotnet from the command line to run the app.
Things break if I have any source modules in a subdirectory. For example, I moved the welcome.ts/html component files into "/src/Pages" and adjusted its route moduleId in app.ts accordingly to "./pages/welcome". The unbundled app then still runs up fine, but when I try the exported version, I get a request being made by SystemJS to http://localhost:5000/dist/pages/welcome.js which 404s (as you'd expect).
I can see the contents of the welcome component in the app-build.js file, and the config.js file within the export folder contains the expected file paths, i.e. it has "Pages/welcome...".
I have read this seemingly similar issue:
https://github.com/aurelia/bundler/issues/131
But setting depCache to false made no difference in my case. Why is SystemJS trying to load this module separately from outside of the bundle?
I was able to reproduce this error locally.
Presuming that you have a Windows environment, it will be a case-sensitivity issue.
After renaming [P]ages folder to [p]ages, bundled version works as expected.
On the filesystem there is a [P]ages/welcome.js viewmodel, but [p]ages/welcome has been defined as moduleId.
Unbundled mode: Windows filesystem is case-insensitive, which behaviour can be misleading by loading [P]ages/welcome.js correctly.
Bundled mode:
Based on file path, bundling process embeds[P]ages/welcome.js as [P]ages/welcome module.
But, according to the route config, SystemJS will be looking for [p]ages/welcome module within app-build.js.
My recommendation would be to use lowercase folder/filenames whenever it's possible.
I'm very new to jenkins. I'm using Jenkins & Robot. Currently, I've written script in perl. Now i'm able to generate 'Xml' file. And also I've generated 'log.html' and 'result.html' .
I need some interpreter to show these reports on jenkins & also charts as well.
I need your help in this.
Install HTML publisher plugin plugin
Refer HTML Publisher Plugin
To display the html in browser
From your job
Select Add Post-build Action->Publish Html Reports
Specify the html path in Html Directory to archieve section
Specify the html to be displayed in IndexPages