Movatterモバイル変換

[0]ホーム
URL:

Wayback Machine
1 capture
16 Jul 2023
JunJULAug
16
202220232024
success
fail
COLLECTED BY
Organization:Archive Team
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.

The main site for Archive Team is atarchiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.

This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by theWayback Machine, providing a path back to lost websites and work.

Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.

The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.

TIMESTAMPS
loading
The Wayback Machine - http://web.archive.org/web/20230716094925/https://github.com/nuxt/nuxt/pull/21863
Skip to content

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

feat(nuxt): polyfillrequestIdleCallback andcancelIdleCallback#21863

Open
logotip4ik wants to merge3 commits intonuxt:main
base:main
Choose a base branch
fromlogotip4ik:feat/expose-idle-callback-polyfill

Conversation

logotip4ik
Copy link

@logotip4iklogotip4ik commentedJun 29, 2023•
edited

🔗 Linked issue

❓ Type of change

  • 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • 👌 Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

ExposesrequestIdleCallback andcancelIdleCallback from#app.
Safari still does not supportrequestIdleCallback. Nuxt uses internal polyfill, thus forcing user to bundle two polyfills if they wanted to userequestIdleCallback. Why not to allow users to use already bundled polyfill ?

📝 Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

danielroe reacted with thumbs up emoji
@codeflowapp
Copy link

Review PR in StackBlitz CodeflowRun & review this pull request inStackBlitz Codeflow.

@danielroe
Copy link
Member

We could conceivably also add them to auto-imports.

logotip4ik reacted with thumbs up emoji

@danielroedanielroe changed the titlefeat: expose idle callback polyfill from#appfeat: polyfillrequestIdleCallback andcancelIdleCallbackJun 29, 2023
@danielroedanielroe added this to the3.7 milestoneJul 9, 2023
Copy link
Member

@danielroedanielroe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Thank you❤️

logotip4ik reacted with heart emoji
@danielroedanielroe changed the titlefeat: polyfillrequestIdleCallback andcancelIdleCallbackfeat(nuxt): polyfillrequestIdleCallback andcancelIdleCallbackJul 9, 2023
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@danielroedanielroedanielroe approved these changes

Assignees
No one assigned
Projects
None yet
Milestone
3.7
Development

Successfully merging this pull request may close these issues.

None yet

2 participants
@logotip4ik@danielroe
[8]ページ先頭
©2009-2025 Movatter.jp