rsnext/packages
JJ Kasper 7054096b76
Move tracing next-server to next build (#30190)
As discussed this moves tracing `next-server` into `next build` since the pre-trace at publish time isn't able to reliably give us file locations since `node_module` file locations can vary based on installation. This also adds caching the trace so that we only need to retrace `next-server` when a lockfile changes. 

A follow-up PR will add documentation for these traces explaining how they can be leveraged. 

## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have 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`
- [ ] Integration tests added
- [ ] Documentation added
- [ ] Telemetry added. In case of a feature if it's used or not.
- [ ] Errors have helpful link attached, see `contributing.md`

## Documentation / Examples

- [ ] Make sure the linting passes by running `yarn lint`
2021-10-22 23:49:38 +00:00
..
create-next-app v11.1.3-canary.95 2021-10-22 08:56:12 -05:00
eslint-config-next v11.1.3-canary.95 2021-10-22 08:56:12 -05:00
eslint-plugin-next v11.1.3-canary.95 2021-10-22 08:56:12 -05:00
next Move tracing next-server to next build (#30190) 2021-10-22 23:49:38 +00:00
next-bundle-analyzer v11.1.3-canary.95 2021-10-22 08:56:12 -05:00
next-codemod v11.1.3-canary.95 2021-10-22 08:56:12 -05:00
next-env v11.1.3-canary.95 2021-10-22 08:56:12 -05:00
next-mdx v11.1.3-canary.95 2021-10-22 08:56:12 -05:00
next-plugin-storybook v11.1.3-canary.95 2021-10-22 08:56:12 -05:00
next-polyfill-module v11.1.3-canary.95 2021-10-22 08:56:12 -05:00
next-polyfill-nomodule v11.1.3-canary.95 2021-10-22 08:56:12 -05:00
react-dev-overlay v11.1.3-canary.95 2021-10-22 08:56:12 -05:00
react-refresh-utils v11.1.3-canary.95 2021-10-22 08:56:12 -05:00