Array.prototype.at for next-polyfill-module

[spiltbeans]

This PR builds on an existing pull request #44436 by @sloanesturz.

This PR address the concerns in the original PR where it was still necessary to add the polyfill to the next-polyfill-module.

Bug

• Related issues linked using fixes #number
• Integration tests added
• Errors have a helpful link attached, see contributing.md

Feature

• Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
• Related issues linked using fixes #number
• e2e tests added
• Documentation added
• Telemetry added. In case of a feature if it's used or not.
• Errors have a helpful link attached, see contributing.md

Documentation / Examples

• Make sure the linting passes by running pnpm build && pnpm lint
• The "examples guidelines" are followed from our contributing doc

[sloanesturz]

Hey @spiltbeans! I have completely lost track of this issue and the solution (I just deleted .at() from my codebase).

Do you mean to add a PR into next.js instead of my fork of it?

[spiltbeans]

Hey @sloanesturz I was looking to fix the polyfill issue you were trying to solve. Your PR just got bumped yesterday so I think others in the community want a solution as well.

From what I understand, your solution hasn't been merged since it only adds code to the next-polyfill-nomodule. (see TkDodo's comment)

I didn't want to submit a duplicate PR into next.js so I thought if I added the missing piece to your branch then maybe your PR would be merged.

So yes, I intended to make a PR to your fork, which I was hoping would go into next.js

[spiltbeans]

Hey @sloanesturz I just want to bump this PR. Do you plan on merging this PR and syncing your branch up with canary? Otherwise I'll open up a duplicate PR in the next.js repo.

Thanks 😄