microsoft
/
accessibility-insights-web
зеркало из https://github.com/microsoft/accessibility-insights-web.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
accessibility-insights-web/packages
История
dependabot[bot] b4de539fa3
chore(deps): Bump luxon from 3.4.4 to 3.5.0 (#7415) 
Bumps [luxon](https://github.com/moment/luxon) from 3.4.4 to 3.5.0.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/moment/luxon/blob/master/CHANGELOG.md">luxon's
changelog</a>.</em></p>
<blockquote>
<h1>3.5.0 (2024-08-03)</h1>
<ul>
<li>Various performance improvements</li>
<li>throwOnInvalid causes the constructor to throw if the year is
invalid</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="a4044fe60e"><code>a4044fe</code></a>
bump to 3.5.0</li>
<li><a
href="cea7b5f7ea"><code>cea7b5f</code></a>
Documented weekSettings opt in DateTime (<a
href="https://redirect.github.com/moment/luxon/issues/1640">#1640</a>)</li>
<li><a
href="2008075eb7"><code>2008075</code></a>
Fixed duplicate word in comment in datetime.js (<a
href="https://redirect.github.com/moment/luxon/issues/1623">#1623</a>)</li>
<li><a
href="cafc4ee159"><code>cafc4ee</code></a>
Perf: Cache ts offset guesses for quickDT (<a
href="https://redirect.github.com/moment/luxon/issues/1579">#1579</a>)</li>
<li><a
href="73c4438852"><code>73c4438</code></a>
fix cutoff year docs</li>
<li><a
href="895a74916a"><code>895a749</code></a>
Added some JS doc for time zones (<a
href="https://redirect.github.com/moment/luxon/issues/1499">#1499</a>)</li>
<li><a
href="080e813122"><code>080e813</code></a>
Alias DateTime in documentation site (<a
href="https://redirect.github.com/moment/luxon/issues/1546">#1546</a>)</li>
<li><a
href="55bdb08f8d"><code>55bdb08</code></a>
add DATETIME_MED_WITH_WEEKDAY to formatting.md (<a
href="https://redirect.github.com/moment/luxon/issues/1554">#1554</a>)</li>
<li><a
href="161611449c"><code>1616114</code></a>
format</li>
<li><a
href="5763215252"><code>5763215</code></a>
Update interval.js doc per <a
href="https://redirect.github.com/moment/luxon/issues/742">#742</a> (<a
href="https://redirect.github.com/moment/luxon/issues/1565">#1565</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/moment/luxon/compare/3.4.4...3.5.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=luxon&package-manager=npm_and_yarn&previous-version=3.4.4&new-version=3.5.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
 		2024-08-12 14:02:22 -04:00
..
axe-config chore: migrate to yarn v3 (#6519) 2023-03-22 17:19:17 -04:00
report chore(deps): Bump luxon from 3.4.4 to 3.5.0 (#7415) 2024-08-12 14:02:22 -04:00
report-e2e-tests chore: Upgrade Typescript version to 5.4.5 (#7294) 2024-05-09 10:38:45 +05:30
ui chore(deps): Bump luxon from 3.4.4 to 3.5.0 (#7415) 2024-08-12 14:02:22 -04:00
validator chore: migrate to yarn v3 (#6519) 2023-03-22 17:19:17 -04:00
README.md feat(remove-android): Update docs (#6755) 2023-06-23 15:38:29 -07:00

README.md

accessibility-insights-web packages

As of Oct 2020, this repository is an ad-hoc monorepo; /src contains code for multiple projects, and does not separate them as cleanly as we would like.

We plan to gradually convert the repository into a Yarn Workspaces based monorepo, similar to how accessibility-insights-service is structured.

Short-term (~Dec 2020) planned package layout

At minimum, we plan to use individual packages for each individually released project:

  • /packages/report: accessibility-insights-report (NPM package, primarily for consumption by accessibility-insights-service)
  • /packages/ui: accessibility-insights-ui (NPM package, primarily for consumption by accessibilityinsights.io)
  • /packages/web: Accessibility Insights for Web (browser extension)

We plan to move end-to-end tests of packages into separate packages, to better test "true" package API boundaries. For example:

  • /packages/report-e2e-tests: End-to-end tests of the report package APIs

Longer term (2021+) plans

Eventually, we could imagine wanting to combine accessibility-insights-service and accessibility-insights-web into one monorepo; we aren't sure whether we necessarily want to do this or not, but in the interest of keeping it easy, we want to lean towards using consistent decisions between the two of them for "directory layout", "which tools run repo-wide vs per-package", etc.

Current (July 2021) package layout

  • /packages/ui: current home of former /src/packages/accessibility-insights-ui/root
  • /packages/report: current home of former /src/reports/package/root
  • /package.json//src: current home of web and most of the build rules for ui/report