additional tlds #8
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
My use case:
Validating a url which is a target of a proxy server and is aliased in /etc/hosts to 127.0.0.1. This url in development mode can have a fake ".local" tld, but in production has a real one.
Another use case is when some new tlds become available and the "tlds" dependency in package.json is not up-to-date.
So:
```javascript
urlRegex({
exact: true,
additionalTlds: env == 'development' ? ['local'] : null
}).test('mysite.' + (env == 'development' ? 'local' : 'com'));
```
|
why not? |
|
It's out of this projects scope. |
|
In my case if I can't pass the "local" tld, I have to use another regex in development... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My use case:
Validating a url which is a target of a proxy server and is aliased in /etc/hosts to 127.0.0.1. This url in development mode can have a fake ".local" tld, but in production has a real one.
Another use case is when some new tlds become available and the "tlds" dependency in package.json is not up-to-date.
So: