Remove documentation about converting the app
This is no longer possible as we now require browser support for modules.
This commit is contained in:
parent
4a8efa6bc9
commit
32222304f4
|
@ -71,24 +71,6 @@ query string. Currently the following options are available:
|
||||||
* `logging` - The console log level. Can be one of `error`, `warn`, `info` or
|
* `logging` - The console log level. Can be one of `error`, `warn`, `info` or
|
||||||
`debug`.
|
`debug`.
|
||||||
|
|
||||||
## Pre-conversion of Modules
|
|
||||||
|
|
||||||
noVNC is written using ECMAScript 6 modules. Many of the major browsers support
|
|
||||||
these modules natively, but not all. By default the noVNC application includes
|
|
||||||
a script that can convert these modules to an older format as they are being
|
|
||||||
loaded. However this process can be slow and severely increases the load time
|
|
||||||
for the application.
|
|
||||||
|
|
||||||
It is possible to perform this conversion ahead of time, avoiding the extra
|
|
||||||
load times. To do this please follow these steps:
|
|
||||||
|
|
||||||
1. Install Node.js
|
|
||||||
2. Run `npm install` in the noVNC directory
|
|
||||||
3. Run `./utils/use_require.js --with-app --as commonjs`
|
|
||||||
|
|
||||||
This will produce a `build/` directory that includes everything needed to run
|
|
||||||
the noVNC application.
|
|
||||||
|
|
||||||
## HTTP Serving Considerations
|
## HTTP Serving Considerations
|
||||||
### Browser Cache Issue
|
### Browser Cache Issue
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue