devtools are not a part of framework and may use `@alpha` for its
traditional meaning. This also resolves issues with `@alpha` referencing
`@beta` APIs, which is not supported for the `/legacy` pattern. (api
export lint policy once enabled will flag that.)
Changes:
* Node10 entrypoints now point to ESM (./lib) for dual-format packages.
* Instead of using '/lib/beta' and '/lib/legacy' as export paths, we now
emit '/beta.d.ts' and '/legacy.d.ts' in the package root.
* We now additionally emit an './internal.d.ts'. ATTW now passes the
full matrix, with select exclusions of test-only exports.
* Miscellaneous trimming / export map fixes.
---------
Co-authored-by: Tyler Butler <tyler@tylerbutler.com>
Co-authored-by: Tyler Butler <tylerbu@microsoft.com>
Co-authored-by: Jason Hartman <jasonha@microsoft.com>
## package.json "exports" coordination
- Only generates where there is presence in "exports".
- Error is generated if there are no matches.
- Requested outputs that are not in "exports" are skipped, with any
prior file being deleted.
- Will now generate an empty export when there are no exports at level
assuming that package.json "exports" are as intended and useless paths
are okay. Will warn (though general build seems to eat most
error/warning logs).
- Removed unused API tasks (can be restored once used)
## Node10 Type Compatibility option
- Node10 types compat stub files are now generated based on package.json
exports and the generated entrypoint files
- Preset from .gitignores
Tested Node10 build compat with a ESNext+Node10 package in FF.
---------
Co-authored-by: Tyler Butler <tyler@tylerbutler.com>
Moves the location from
`<root>/_api-extractor-temp-<version>/doc-models` to
`docs/_doc-models/<version>`.
Also removes `readVersionData.js`, which is unused.
Added download option in docs/package.json to download all api doc
versions from azure storage.
This download step is necessary for testing multi api version docs
locally, as api-extractor would only generate api docs for the local
repo.
This prevents 'prettier' from emitting warnings for files in
'.pnpm-store/' when building the GitRest and Historian services per the
dev instructions in the README.md.
Because the dependencies required to build these services are tricky to
install locally (esp. on non-Linux systems), the README for these
services recommends:
* Building the service in a Docker container
* Mounting the 'gitrest/' or 'historian/' directories from the local
filesystem into the container.
* Running 'bash' inside the container to run 'pnpm i' and 'pnpm run
build'
A side effect or running 'pnpm i' with the local file system mount as
described above is that it places the '.pnpm-store' cache in the build
directory, causing 'prettier' to include this directory while scanning.
Removes the UPCOMING.md file and associated build tasks.
As implemented, the file can conflict a lot even with main branch
commits (since there are changesets added all the time), and there is
conflicting information about whether partners actually find a roll up
of upcoming _unreleased_ changes useful.
The file can still be generated manually if needed. This might be useful
for the release driver to create release notes. Also, we will still
create changelogs for each package. This change only affects
upcoming.md.
We can also still consider producing a page for the website with this
info.
Alfred, Deli, Scriptorium, Copier, Scribe, and Riddler need to specify
platform 'linux/amd64'.
All MacOS users will need to disable 'Airplay Receiver' to free port
5000 for Riddler (added to README.md)
This change updates the type validation tooling to support multiple versions in the package json broken definitions. This changes the format, so existing package json type validation was updated, and all tests were re-generated
related to #7614
Second part of #2449
Add a build-tools script to collect generated bundle analysis reports for use in an ADO pipe. Followup will add a command in the package.json to run it once this gets published.
First part of #2449
Add webpack steps to packages/hosts/base-host and server/gateway that output a size analysis. Once this is in, the ADO pipe that publishes the size analysis artifacts can be added.
Using base-host and gateway here because base-host covers most (all?) the client packages, while gateway covers most server packages (less sure on how useful gateway is though since it's not up to date on server dependencies)
These packages are shared amongst client and server code. Pulling them out of client code so we don't have circular dependencies between the mono-repo.
The packages can be built locally via npm scripts at the root. server/routerlicious will use docker to build the packages as well (on top of composing the server)
Also moved shared/test-utils and shared/tools-core to server as they are only used by the server.
packages/server will eventually move out in the future when we are ready to independently rev the versions
- Redis session support + Google login
- Fix some Google auth bugs
- Add in MSFT v2 oauth flow
- Use request to pull in user information from a microsoft accoutn load
- Move DocumentDB related functionality to a db folder
- Get source maps working and fix up some bugs in auth flow
- Add account linking
- Add in some HTML templates
- Flesh out the login/logout behavior
- Add ability to unlink an account
...
Jason Hartman
Daniel Lehenbauer
Joshua Smithrud
Michael Zhen
Tyler Butler
Tony Murphy
Elchin Valiyev
Alex Panov
Helio Liu
Curtis Man
Kurt Berglund
Ian Williams
Steven Lucco