Package Exports
- is-valid-hostname
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (is-valid-hostname) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
is-valid-hostname
Validate hostname in JavaScript based on RFC-1123.
Demo
https://lab.miguelmota.com/is-valid-hostname
Install
npm install is-valid-hostnameUsage
const isValidHostname = require('is-valid-hostname')
isValidHostname('localhost') // true
isValidHostname('example.com') // true
isValidHostname('foo.example.com') // true
isValidHostname('bar.foo.example.com') // true
isValidHostname('exa-mple.co.uk') // true
isValidHostname('xn--80ak6aa92e.com') // true
isValidHostname('9gag.com') // true
isValidHostname('8.8.8.8') // true
isValidHostname('127.0.0.1') // true
isValidHostname('exa_mple.com') // false
isValidHostname('-example.com') // false
isValidHostname('example.com:3000') // false
isValidHostname('8.8.8.8:3000') // falseView more examples.
Test
npm testFAQ
Q: Why are numbers allowed in top-level domain?
- A: Numbers in TLD are allowed under RFC-1123. See this answer for more information.