Conversation
Updated: - parse-domain from ^5.0.0 to 6.0.0 For issues or feature requests: <support@depshub.com>
![depshub-app[bot]](https://avatars.githubusercontent.com/in/338422?s=60&v=4){kind=small}
| // "referenced_tweets.id.author_id", | ||
| // "entities.mentions.username", | ||
| ].join(","), | ||
| "tweet.fields": [ |
There was a problem hiding this comment.
Package parse-domain version 8.0.0 has the following breaking changes:
Dropped official support for Node 12, 14 and 16. There wasn't any actual breaking change we know of but use at your own risk :)
| } | ||
| return numeral(num).format("0,0"); | ||
| }); | ||
| }; |
There was a problem hiding this comment.
Package parse-domain version 8.0.0 has the following breaking changes:
Dropped official support for Node 12, 14 and 16. There wasn't any actual breaking change we know of but use at your own risk :)
| data.avatar = `https://v1.indieweb-avatar.11ty.dev/${encodeURIComponent(data.homeUrl)}/`; | ||
|
|
||
| module.exports = data; No newline at end of file | ||
| null |
There was a problem hiding this comment.
Package parse-domain version 7.0.0 has the following breaking changes:
parseDomain won't .trim() the given input. The input is interpreted as it is. If you want to trim the input, you need to call .trim() before passing it to parseDomain. Auto-trimming the input changes the domain and might not be desired if any character (such as whitespace) is allowed (e.g. when using lax validation).
| module.exports = function(text, replacementText) { | ||
| return text.replace( /\<[^\>]*\>/g, replacementText || "" ); | ||
| }; No newline at end of file | ||
| null |
There was a problem hiding this comment.
Package parse-domain version 7.0.0 has the following breaking changes:
parseDomain won't .trim() the given input. The input is interpreted as it is. If you want to trim the input, you need to call .trim() before passing it to parseDomain. Auto-trimming the input changes the domain and might not be desired if any character (such as whitespace) is allowed (e.g. when using lax validation).
| } | ||
| return numeral(num).format("0,0"); | ||
| }); | ||
| }; |
There was a problem hiding this comment.
Package parse-domain version 6.0.0 has the following breaking changes:
parse-domain will now be released as native ECMAScript module. There's no CommonJS build anymore. If you're still using CommonJS, you need to import it asynchronously using
await import("parse-domain"). If you're still using Node 12, you may need to update it to the latest 12.x version.
| @@ -1,5 +1,4 @@ | |||
| const Sentiment = require("sentiment"); | |||
| const { parseDomain } = require("parse-domain"); | |||
| const dataSource = require("./DataSource"); | |||
There was a problem hiding this comment.
Package parse-domain version 6.0.0 has the following breaking changes:
parse-domain will now be released as native ECMAScript module. There's no CommonJS build anymore. If you're still using CommonJS, you need to import it asynchronously using
await import("parse-domain"). If you're still using Node 12, you may need to update it to the latest 12.x version.
This pull request was created automatically by DepsHub.
Please review the changes and merge them if they look good.
The following packages were updated:
View details.