Dear noVNC community,--Thanks a lot for an amazing tool! We use it on https://janitor.technology to allow anyone to easily hack on large projects like Firefox, Servo, Thunderbird, Chromium and others.Unfortunately, noVNC stopped working for our Chrome users a while back (related to the introduction of Babel around commit [0], see GitHub issue [1]). We believe that the main problem is that we're using noVNC's Babel in production, while we should be serving a compiled production-grade noVNC app instead as suggested by Solly Ross.Today, we install noVNC simply by cloning the repository [2], calling launch.sh [3], and then serving /vnc_auto.html (which was recently renamed to /vnc_lite.html).Instead, we would like to build a production-grade noVNC front-end, e.g. with `node ./utils/use_require.js --as commonjs`, but we don't know how to properly serve the transpiled files:- What is the best way to serve a /vnc.html or /vnc_lite.html that uses the transpiled files in /lib?- Can one of the scripts in /utils do this for us?- Do we need to hack a special production-ready "/lib/vnc.html"?Bonus question (unrelated): Is there already a good noVNC integration/plugin for Cloud9 IDE? [4]Many thanks!Jan[4] https://c9.io
You received this message because you are subscribed to a topic in the Google Groups "noVNC" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/novnc/FfksNkEMgPo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to novnc+unsubscribe@googlegroups.com.
To post to this group, send email to no...@googlegroups.com.
Visit this group at https://groups.google.com/group/novnc.
For more options, visit https://groups.google.com/d/optout.