This is a good first PR!

We should add some tests to cover #7036. They should cover both JavaScript and TypeScript support.

They can probably be added to test/fixtures.

Some of the issues below are already mentioned in other tickets, but I have the feeling that a proper generic issue is due to give it visibility, as for now the current package is unusable for many users.

1. The typescript package doesn't respect the tsconfig flags, and many of them are hardcoded inside the meteor/babel package.
   I understand that meteor needs to control some compilation option

Bug Report

From the docs section Add favicon and metadata

Comment in code example states for "The doc prop contains some metadata about the page being rendered that you can use."

// The doc prop contains some metadata about the page being rendered that you can use.
const Wrapper = ({ children, doc }) => <React.Fragment>
  

How to let server in ubuntu print log?

suggest： Output specific logs when be scanned, record the scanner's IP，use fail2ban ban scanner ip.

Prerequisites

• Did you check the wiki?
• Did you search in issues?
• Are you running the latest version?
• I will write this according to

This would be very helpful for idiots like me who don’t know what they are doing.

Google Docs tracks users heavily. Why not use GitHub wiki, if you redirect age-encryption.org/ to GitHub anyway?

Also, a real textual format (markdown) would help a lot! Gdocs is a pain to read.

Feature Request

Is your feature request related to a problem? Please describe.

The Preact Section in the readme, as they are out of date. Preact v10 has a proper hydrate method now. PR: preactjs/preact#1802.

Describe the solution you'd like
Update the

I find it a bit awkward that for @babel/preset-env to use a .browserslistrc file (which is @babel/preset-env's default behavior when no targets is passed), I have to remember to pass targets: false: https://github.com/neutrinojs/neutrino/blob/master/packages/web/index.js#L116-L128

A the very least, I propose we look for a browserslist file, and if one is present, output a notice the con

Feature Request

Right now when you run npm run build, the code is obfuscated and doesn't work with WP CLI's makepot feature because the variables are overwritten to be something else.

Adding this to webpack.config.prod.js allows for the i18n strings to not be obfuscated so that a user can run WP CLI's makepot command and have the JavaScript strings added to their POT file.

I recognize this is a special case so feel free to not support it!

I'm trying to get A-Frame (a webVR library) running within x0. It works with the development server:

Unfortunately after running x0 build docs --static

My repo which I installed php from does not defaultly ship with json plugin, I must manually install it to make it works.
So if you can clarify not only json plugin but all plugins we must have, then newcomers would have less asspain.

The readme features basic documentation for Sockends, and doesn't give a complete example for how and why it works. Therefore we need more detailed documentation in the readme. Certain things like simple security mechanisms via respondsTo and broadcasts configurations should also be taken into account.

This issue is tracking the documentation that has to be updated.

• Document new platform commands
• Update the section dedicated to page <title> and tell about [Browser.documen

npx create-react-app example --typescript
cd ./example

create jetpack.config.js from doc

jetpack --verbose
jetpack › Jetpack 0.12.1 �
jetpack › Webpack 4.28.3
jetpack › Dir G:\source\example
jetpack › Entry .
jetpack › Asset server http://localhost:3030
jetpack › Failed to compile! 

On github it is common to include images in the README.md, like so:

https://git.s-ol.nu/janko-keystep-rgb/blob/master/README.md

![](doc/wiring.png)

this currently creates the right markup:

<img alt="" src="doc/wiring.png">

however the browser then request the image at https://git.s-ol.nu/janko-keystep-rgb/blob/master/doc/wiring.png, where he gets served the HTML page showi

I'm submitting a ...

• bug report
• feature request
• support request

What is the current behavior?

Keyboard control works great, but still lacking many accessibility features.

What is the expected behavior?

vue-simple-suggest to be more screen reader friendly.

Including:

• Necessary aria tags
• Using a ul and li tags for suggestions