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

Migrate @newrelic/next into repo #2127

Closed
jsumners-nr opened this issue Apr 4, 2024 · 3 comments
Closed

Migrate @newrelic/next into repo #2127

jsumners-nr opened this issue Apr 4, 2024 · 3 comments
Assignees
Labels
semver: major Backwards incompatible changes.

Comments

@jsumners-nr
Copy link
Contributor

jsumners-nr commented Apr 4, 2024

See #2123.

Note: we should mark it as experimental in the release notes and as an on-going basis.

Tasks:

  • deprecate the @newrelic/next package
  • Update lib/instrumentations.js to register a relative folder
  • Remove the external versioned tests configuration.
  • update tests to use test/lib/agent_helper instead of @newrelic/test-utilities
  • Convert git history with the previous repo.
  • Archive old repo when done.
@workato-integration
Copy link

@bizob2828
Copy link
Member

This is fine but I think we should wait to do this until we've deemed our instrumentation stable

@bizob2828
Copy link
Member

If we do this, it's more than just migrating the next.js instrumentation into the repo. We had a bunch of FAQs around Next.js nuance and would have to port those and the standalone to externalize libraries

@bizob2828 bizob2828 added the semver: major Backwards incompatible changes. label Jun 27, 2024
@bizob2828 bizob2828 moved this to Triage Needed: Unprioritized Features in Node.js Engineering Board Jul 15, 2024
@kmudduluru kmudduluru moved this from Triage Needed: Unprioritized Features to To do: Features here are prioritized for this sprint (jira for remaining tickets) in Node.js Engineering Board Jul 23, 2024
@bizob2828 bizob2828 self-assigned this Jul 26, 2024
@bizob2828 bizob2828 moved this from To do: Features here are prioritized for this sprint (jira for remaining tickets) to In progress: Issues being worked on in Node.js Engineering Board Jul 26, 2024
@github-project-automation github-project-automation bot moved this from In progress: Issues being worked on to Done: Issues recently completed in Node.js Engineering Board Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver: major Backwards incompatible changes.
Projects
Archived in project
Development

No branches or pull requests

2 participants