If you don’t follow our rules, your project will not be built • The Registry
Google’s Chrome team has introduced projects to help framework authors with what they see as best practices, primarily starting with React-based Next.js.
A team of six people (apparently known internally as WebSDK) working on Chrome presented what they called the project. Dawn earlier this week, described as a “collaboration with the authors of the framework”. The article talks about the benefits of “strong defaults and smart tools,” based on experience with Google applications such as search and maps.
Work already done includes an image component for Next.js, then ported to Nuxt, inline CSS for web fonts for Next.js and Angular, and a custom plugin for ESLint support (static analysis ) in Next.js.
Therefore, the team designed a set of static code analysis and dynamic checks rules, covering several “surfaces” including ESLint, TypeScript, dynamic checks on the user’s development server, the Webpack bundler. and CSS tools. Developers who break the rules will receive warnings to correct the code, while “at build time, unresolved issues of high severity will prevent a successful build.” Translation: violating good Compliance practices will prevent the construction of a project. This is, we’re guessing, the reason the project is called Conformance, or should it be “Google knows best?”
These innovations are coming first on Next.js, which is why these projects were presented to the world at the same time as the Next.js Conf this week. During the event, Next.js 11 was released, with Conformance boasted as “a system that provides carefully designed solutions to support optimal UX.”
This, along with the improved performance and adoption of Webpack 5 by default, were touted as the strengths of the new version. Vercel, sponsor of Next.js, also presented a React application conversion project started with the Create a React app command to be compatible with Next.js, and a preview of a new browser-based, cloud-hosted coding environment called Next.js Live.
Google’s initiatives with Aurora and Conformance are in a sense an advantage for the web development community, in that they should improve performance and user experience by optimizing the libraries used by developers, which is normally out of the question. scope of a team working on the browser platform.
There are caveats, however. Google’s apparent preference for Next.js may increase the momentum behind this framework at the expense of alternatives, and although in their Aurora article, the team said their job is to “deliver the best possible user experience for apps. production, regardless of which browser you use. rendering, “it’s hard to escape the idea that Google is building an optimized stack based on Chrome and Next.js.
An intriguing paragraph in the compliance article states: “Compliance is first explored in Next.js with the aim of expanding to other frameworks (Nuxt, Angular, etc.). ESLint and TypeScript are already used in many frameworks in different ways, but the concept of a consistent browser-level execution system is being actively explored. “