eecc3342cb
This pull request **temporarily** removes ESLint, as it was not landed in accordance with our standard experimental policies. We are fully committed to landing this change again. This is being reverted because: - Next.js has very strict goals for its install size. This feature resulted in adding over 17MB, or a 43.6% increase. - The feature was not first landed under the `experimental` key in `next.config.js`, rather, it was added under the stable namespace (top-level) - Using the feature doesn't do a "guided setup" like TypeScript, it should ask you to "bring your own" dependencies for ESLint - It uses a undesirable ESLint plugin name: `plugin:@next/next/recommended`. This should read out as strictly `next`, or as short as we can get it. - Does not provide actionable warnings (missing link to resolve issue) - Does not follow appropriate console output styling. We need to revisit how these are presented. To re-land this, we need to ensure the following minimums are met: - Very minor change in install size - Fully experimental (i.e. flagged) with warnings - Finalized package name and configuration shape, preferably so we can do ` { extends: 'next' } `. |
||
---|---|---|
.. | ||
lib | ||
api-utils.ts | ||
config-shared.ts | ||
config-utils.ts | ||
config.ts | ||
crypto-utils.ts | ||
denormalize-page-path.ts | ||
font-utils.ts | ||
get-page-files.ts | ||
get-route-from-entrypoint.ts | ||
image-config.ts | ||
image-optimizer.ts | ||
incremental-cache.ts | ||
load-components.ts | ||
next-server.ts | ||
node-polyfill-fetch.js | ||
normalize-page-path.ts | ||
optimize-amp.ts | ||
render.tsx | ||
require.ts | ||
router.ts | ||
send-payload.ts | ||
serve-static.ts | ||
utils.ts |