Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(next): shim more api #444

Merged
merged 7 commits into from
Jun 27, 2024
Merged

feat(next): shim more api #444

merged 7 commits into from
Jun 27, 2024

Conversation

hi-ogawa
Copy link
Owner

@hi-ogawa hi-ogawa commented Jun 26, 2024

Trying to get this example compiled at least, then later we can consider actual implementation:

Copy link
Owner Author

hi-ogawa commented Jun 26, 2024

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @hi-ogawa and the rest of your teammates on Graphite Graphite

@hi-ogawa hi-ogawa changed the title feat(next): more shim feat(next): shim more api Jun 26, 2024
@hi-ogawa hi-ogawa marked this pull request as ready for review June 27, 2024 00:15
Copy link
Owner Author

hi-ogawa commented Jun 27, 2024

Merge activity

  • Jun 26, 9:23 PM EDT: @hi-ogawa started a stack merge that includes this pull request via Graphite.
  • Jun 26, 9:27 PM EDT: Graphite rebased this pull request as part of a merge.
  • Jun 26, 9:28 PM EDT: @hi-ogawa merged this pull request with Graphite.

@hi-ogawa hi-ogawa force-pushed the feat-auto-setup-tsconfig-paths branch from a32503e to 760b573 Compare June 27, 2024 01:24
Base automatically changed from feat-auto-setup-tsconfig-paths to main June 27, 2024 01:26
@hi-ogawa hi-ogawa force-pushed the feat-next-more-compat branch from 0774360 to 70a4b03 Compare June 27, 2024 01:26
@hi-ogawa hi-ogawa merged commit 3509795 into main Jun 27, 2024
6 checks passed
@hi-ogawa hi-ogawa deleted the feat-next-more-compat branch June 27, 2024 01:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant