Specify the useRuntimes property for the "remix" framework to use the @vercel/remix Builder.

The ENABLE_FILE_SYSTEM_API env var is no longer necessary so the vercel.json file from the Remix template has also been deleted.

Describe the feature you'd like to request

A starter example component library where each component is published as its own NPM package.

Describe the solution you'd like

• Turborepo
• SWC for compilation and test running (through Jest)
• Package publishing (could be Lerna or something else)
• ESLint
• TypeScript
• A way to view components

Describe alternatives you've considered

Maybe tsup is a better solution here? Open to suggestions.

Storybook doesn't seem like the right choice because it brings in webpack and Babel and ideally this solution avoids those entirely.

I know this PR is a relatively large and unsolicited change, but I found a few inconsistencies in ESLint plugin documentation, etc. I thought might be worth fixing. As such, I'll take no offense if y'all don't want all or any of it.

Please let me know if you'd like anything changed.

• Adds missing ESLint rules to rules table.
  • no-duplicate-head
  • ~no-script-in-document~ no-before-interactive-script-outside-document
  • no-script-in-head
  • no-server-import-in-page
• Adds missing @next prefix to rules table (needed to override rules and it's misleading as is).
• Adds missing metadata for some rules.
  • no-css-tags
  • no-sync-scripts
• Adds rule descriptions to rule error message pages.
• Changes rule descriptions, error messages, message page urls, and message page titles, to be consistent with one another.
• Changes rules in index.js and in eslint.md rules table to be alphabetized for better readability (and for rule reconciliation as it matches the file system).
• Changes 1s and 2s in index.js to be 'warn' and 'error', respectively, for better readability.
• Changes recommended config to group errors and warnings together for better readability.

Feature

• Documentation added
• Errors have helpful link attached, see contributing.md

Documentation / Examples

• Make sure the linting passes by running yarn lint

Fixes this issue https://github.com/vercel/micro-dev/issues/87 by native-way

Fixes this issue https://github.com/vercel/micro-dev/issues/87 by native-way

Hi, I found the example of socket.io-chat-app using jQuery for DOM manipulation and I thought it would be better to use vanilla JS instead of JQuery for DOM. Thank you.

This PR adds VuePress and VitePress the list of supported frameworks.

• https://vuepress-starter-template.vercel.app
• https://vitepress-starter-template.vercel.app

Tests

• The code changed/added as part of this PR has been covered with tests
• All tests pass locally with yarn test-unit