diff --git a/lib/devtools.js b/lib/devtools.js index a935e19..d6b8df0 100644 --- a/lib/devtools.js +++ b/lib/devtools.js @@ -80,38 +80,48 @@ customElements.define('developer-tooling', class extends HTMLElement { font-size: .9em; } pre > code { display: block; line-height: 1.025rem; padding-left: 1em; background: #181e19 } + h1, h2, h3, h4, h5, h6 { font-weight: bold; } + h1 { font-size: 1.6rem; } + h2 { font-size: 1.4rem; } + h3 { font-size: 1.2rem; } + h4 { font-size: 1rem; } + h5 { font-size: .8rem; } + h6 { font-size: .7rem; } + h1 { padding: .5rem; border-right: 1px solid #B0D944; border-bottom: 1px solid #B0D944; display: inline-block; padding-right: 0.75em; padding-left: 0.5em; }
Some application setup is required to enable remote debugging
- First install the pear-inspect module into the application
npm install pear-inspect
- Then add the following JavaScript code to the application, at the top:
+Some application setup is required to enable remote debugging
+ Install the pear-inspect module into the application
npm install pear-inspect
+ Add the following code to the application, before any other code:
-if (Pear.config.dev) {
+ if (Pear.config.dev) {
const { Inspector } = await import('pear-inspect')
const inpector = await new Inspector()
const key = await inpector.enable()
console.log('Pear Inspector key:', key.toString('hex'))
}
- When the application is opened in development mode the inspection key will be logged.
- Paste the logged key into the input and use a compatible inspect protocol tool, such as chrome://inspect to view the remote target
+ When the application is opened in development mode the inspection key will be logged.
+ Paste the logged key into the input and use a compatible inspect protocol tool, such as chrome://inspect to view the remote target
+