iotStudio
iotStudio copied to clipboard
dgiot
chore(deps-dev): bump css-loader from 3.6.0 to 5.2.7
Bumps css-loader from 3.6.0 to 5.2.7.
Release notes
Sourced from css-loader's releases.
v5.2.7
5.2.7 (2021-07-13)
Bug Fixes
- fix crash when source map is unavailable with external URL in
[@import](https://github.com/import)(bb76fe4)v5.2.6
5.2.6 (2021-05-24)
Bug Fixes
v5.2.5
5.2.5 (2021-05-20)
Bug Fixes
v5.2.4
5.2.4 (2021-04-19)
Bug Fixes
v5.2.3
5.2.3 (2021-04-19)
Bug Fixes
- improve performance
v5.2.2
5.2.2 (2021-04-16)
Bug Fixes
- avoid escape nonASCII characters in local names (0722733)
v5.2.1
5.2.1 (2021-04-09)
... (truncated)
Changelog
Sourced from css-loader's changelog.
5.2.7 (2021-07-13)
Bug Fixes
- fix crash when source map is unavailable with external URL in
[@import](https://github.com/import)(bb76fe4)5.2.6 (2021-05-24)
Bug Fixes
5.2.5 (2021-05-20)
Bug Fixes
5.2.4 (2021-04-19)
Bug Fixes
5.2.3 (2021-04-19)
Bug Fixes
- improve performance
5.2.2 (2021-04-16)
Bug Fixes
- avoid escape nonASCII characters in local names (0722733)
5.2.1 (2021-04-09)
Bug Fixes
5.2.0 (2021-03-24)
... (truncated)
Commits
ae98845chore(release): 5.2.7bb76fe4fix: fix crash when source map is unavailable with external URL in@importadcc438ci: useactions/setup-node@v2(#1323)c7f81ebchore: fix typo (#1318)d31c680chore(release): 5.2.6075d9bdfix: always write locals export when css modules/icss enabled (#1315)fa9d4c4chore(release): 5.2.50cf8cdefix: compatibility with named export and es5 (#1314)8f1a6fcchore:huskyupdated (#1312)417aabadocs: recommend (#1313)- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "Published by a pub.dev verified publisher"){kind=small}
Example Check Group #2 (Click here to edit)
- [ ] Modify this checklist and click on the save button for it to appear on Github Pull Requests for this repo
- [ ] If you would like the checklist state to roll up to the Pull Request status, select the Enforce on Merge checkbox
![pull-checklist[bot] avatar](https://avatars.githubusercontent.com/in/50375?v=4 "Published by a pub.dev verified publisher"){kind=small}
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Updated |
|---|---|---|---|
| dgiot-dashboard | ✅ Ready (Inspect) | Visit Preview | Aug 15, 2022 at 5:31AM (UTC) |
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!
Quantification details
Label : Extra Small
Size : +1 -1
Percentile : 0.8%
Total files changed: 1
Change summary by file extension:
.json : +1 -1
Change counts above are quantified counts, based on the PullRequestQuantifier customizations.
Why proper sizing of changes matters
Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean:
- Fast and predictable releases to production:
- Optimal size changes are more likely to be reviewed faster with fewer iterations.
- Similarity in low PR complexity drives similar review times.
- Review quality is likely higher as complexity is lower:
- Bugs are more likely to be detected.
- Code inconsistencies are more likely to be detected.
- Knowledge sharing is improved within the participants:
- Small portions can be assimilated better.
- Better engineering practices are exercised:
- Solving big problems by dividing them in well contained, smaller problems.
- Exercising separation of concerns within the code changes.
What can I do to optimize my changes
- Use the PullRequestQuantifier to quantify your PR accurately
- Create a context profile for your repo using the context generator
- Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the
Excludedsection from yourprquantifier.yamlcontext profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your
prquantifier.yamlcontext profile. - Only use the labels that matter to you, see context specification to customize your
prquantifier.yamlcontext profile.
- Change your engineering behaviors
- For PRs that fall outside of the desired spectrum, review the details and check if:
- Your PR could be split in smaller, self-contained PRs instead
- Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).
- For PRs that fall outside of the desired spectrum, review the details and check if:
How to interpret the change counts in git diff output
- One line was added:
+1 -0 - One line was deleted:
+0 -1 - One line was modified:
+1 -1(git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.
Was this comment helpful? :thumbsup: :ok_hand: :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.
![pull-request-quantifier-deprecated[bot] avatar](https://avatars.githubusercontent.com/in/93966?v=4 "Published by a pub.dev verified publisher"){kind=small}
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.