You can edit almost every page by Creating an account. Otherwise, see the FAQ.

Next.js

From EverybodyWiki Bios & Wiki


Next.js
The Next.js logo, a stylization of it's name
Next.js logo
Original author(s)Guillermo Rauch[1]
Developer(s)Vercel and open-source community[2]
Initial releaseOctober 25, 2016; 8 years ago (2016-10-25)[3]
Stable release
9.5.5 / 10 October 2020; 4 years ago (2020-10-10)
Preview release
9.5.6 Canary
Repositorygithub.com/vercel/next.js
Written inJavaScript and TypeScript
Engine
    PlatformWeb platform
    Included withReact
    Size17.0 MB
    TypeWeb application framework
    LicenseMIT License
    Alexa rankSteady 7212 (October 2020)[4]
    Websitenextjs.org

    Search Next.js on Amazon.

    Next.js is an open-source React front-end development web framework that enables functionality such as server-side rendering and generating static websites for React based web applications. It is a production-ready framework that allows developers to quickly create static and dynamic JAMstack websites and is used widely by many large companies.[5] Next.js is one of several recommended "toolchains" available when starting a new React app, all of which provide a layer of abstraction to aid in common tasks. Traditional React apps render all their content in the client-side browser, Next.js is used to extend this functionality to include applications rendered on the server side. The copyright and trademarks for Next.js are owned by Vercel.[6] On July 27, 2020 Next.js version 9.5 was announced, adding new capabilities including incremental static regeneration, rewrites, and redirect support.

    Background[edit]

    Next.js is a React framework that enables several extra features, including server-side rendering and generating static websites.[7] React is a web framework that is traditionally used to build web applications rendered in the client's browser with Javascript.[8] Developers recognize several problems with this strategy however, such as not catering to users who do not have access to javascript or have disabled it, potential security issues, significantly extended page loading times, and it can harm the site's overall search engine optimization.[8] Frameworks such as Next.js sidestep these problems by allowing some or all of the website to be rendered on the server-side before being sent to the client.[8][9] Next.js is one of the most popular components available in React.[10] It is one of several recommended "toolchains" available when starting a new app, all of which provide a layer of abstraction to aid in common tasks.[11] Next.js requires Node.js and can be initialized using Node Package Manager.

    Google has donated to the Next.js project, contributing 43 pull requests in 2019 where they helped in pruning unused JavaScript, reducing overhead time, and adding improved metrics.[12] As of March 2020, the framework is used by many large websites, including Netflix, Docker, GitHub, Uber, and Starbucks.[8] In early 2020, it was announced that Vercel had secured twenty-one million dollars in Series A funding to support improvements to the software.[1] The framework's original author, Guillermo Rauch, is currently the CEO of Vercel and the projects lead developer is Tim Neutkens.[13]

    Development history[edit]

    Next.js was first released as an open-source project on GitHub on October 25, 2016; 8 years ago (2016-10-25).[3] It was originally developed based on six principles: out-of-the box functionality requiring no setup, JavaScript everywhere, all functions are written in JavaScript, automatic code-splitting and server-rendering, configurable data-fetching, anticipating requests, and simplifying deployment.[14] Next.js 2.0 was announced in March 2017 including several improvements that made it easier to work with small websites. It also increased the build efficiency and improved the scalability of the hot-module replacement feature.[15] Version 7.0 was released in September of 2018 with improved error handling and support for React's context API for improved dynamic route handling. This was also the first version to upgrade to webpack 4.[16] Version 8.0 was released in February 2019 and was the first version to offer serverless deployment of applications, in which the code is split up into lambda functions that are ran on demand. The version also reduced the time and resources required for static exports and imporved prefetch performance.[17] Version 9.3, announced in March 2020, included various optimizations and global Sass and CSS module support.[18] On July 27, 2020 Next.js version 9.5 was announced, adding new capabilities including incremental static regeneration, rewrites, and redirect support.[19]

    Styling and features[edit]

    The Next.js framework utilizes JAMstack architecture, which distinguishes between front-end and back-end and allows for efficient front-end development that is independent of any back-end APIs.[1] The framework supports common CSS as well as precompiled Scss and Sass, CSS-in-JS, and styled JSX.[11] In addition, it is built with TypeScript support and smart bundling.[20] The framework integrates with Redux for state management and uses the GraphQLquery language for API calls.[8] The software uses Redux's "store" to hold information about the state of the application, which is updated sequentially to avoid read-write conflicts.[8] The open source transpiler Babel is used to transform and compile code into JavaScript usable by a browser. Webpack, another open-source tool, is used to bundle the modules afterwards. All of these tools are used with npm in a terminal.[12]

    The main feature of Next.js is its use of server-side rendering to reduce the burden on web browsers and provide enhanced security. This can be done for any part of the application or the entire project, allowing for content-rich pages to be singled out for server-side rendering.[8] It can also be done only for first time visitors, to reduce the burden on web browsers that have yet to download any of the site's assets.[9] The "hot reloading" feature detects changes as they are made and re-renders the appropriate pages so they server avoids the need to be restarted. This allows changes made to the application code to be immediately reflected in the web browser, though some browsers will require the page to be refreshed.[8] The software uses page-based routing for developer convenience and includes support for dynamic routing. Other features include hot-module replacement so that modules can be replaced live, automatic code splitting, which only includes code necessary to load the page, and page prefetching to reduce load time.[8]

    See also[edit]

    Some use of "" in your query was not closed by a matching "".Some use of "" in your query was not closed by a matching "".

    References[edit]

    1. 1.0 1.1 1.2 April 21, Matt Asay in Developer on; 2020; Pst, 9:51 Am. "How Next.js aims to simplify front-end development". TechRepublic. Retrieved 2020-10-20.
    2. "zeit/next.js". GitHub. Archived from the original on 2019-03-16. Retrieved 2019-03-17. Unknown parameter |url-status= ignored (help)
    3. 3.0 3.1 "Next.js First Release". GitHub. 2019-03-14. Archived from the original on 2020-10-10. Retrieved 2019-03-17. Unknown parameter |url-status= ignored (help)
    4. "nextjs.org Competitive Analysis, Marketing Mix and Traffic - Alexa". www.alexa.com. Retrieved 2020-10-20.
    5. "How To Build A Blog With Next And MDX". Smashing Magazine. 2020-09-09. Retrieved 2020-10-19.
    6. "Develop. Preview. Ship. For the best frontend teams – Vercel". vercel.com. Archived from the original on 2020-10-01. Retrieved 2020-09-22. Unknown parameter |url-status= ignored (help)
    7. "Differences Between Static Generated Sites And Server-Side Rendered Apps". Smashing Magazine. 2020-07-02. Retrieved 2020-10-19.
    8. 8.0 8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 Thakkar, Mohit (2020), Thakkar, Mohit, ed., "Next.js", Building React Apps with Server-Side Rendering: Use React, Redux, and Next to Build Full Server-Side Rendering Applications, Berkeley, CA: Apress, pp. 93–137, doi:10.1007/978-1-4842-5869-9_3, ISBN 978-1-4842-5869-9, retrieved 2020-10-20
    9. 9.0 9.1 Thakkar, Mohit (2020), Thakkar, Mohit, ed., "Adding Server-Side Rendering to Your React Application", Building React Apps with Server-Side Rendering: Use React, Redux, and Next to Build Full Server-Side Rendering Applications, Berkeley, CA: Apress, pp. 139–152, doi:10.1007/978-1-4842-5869-9_4, ISBN 978-1-4842-5869-9, retrieved 2020-10-20
    10. December 2, Matt Asay in Developer on; 2019; Pst, 11:58 Am. "Why front-end development may be the new frontier". TechRepublic. Retrieved 2020-10-20.
    11. 11.0 11.1 "Comparing Styling Methods In Next.js". Smashing Magazine. 2020-09-17. Retrieved 2020-10-20.
    12. 12.0 12.1 January 31, Matt Asay in Developer on; 2020; Pst, 6:33 Pm. "An insider's look at Google's web framework contributions to Next.js and more". TechRepublic. Retrieved 2020-10-19.
    13. "Static site generation with single page app functionality? That's what's coming Next(.js)". Stack Overflow Blog. 2020-10-07. Retrieved 2020-10-20.
    14. Krill, Paul (2016-10-31). "Next step after Node.js: Framework for 'universal' JavaScript apps". InfoWorld. Retrieved 2020-10-20.
    15. Krill, Paul (2017-03-28). "Next.js 2.0 plays better with React and JavaScript". InfoWorld. Retrieved 2020-10-20.
    16. Krill, Paul (2018-09-21). "Next.js 7 framework compiles faster, supports WebAssembly". InfoWorld. Retrieved 2020-10-20.
    17. Krill, Paul (2019-02-14). "Next.js 8 now supports serverless apps". InfoWorld. Retrieved 2020-10-20.
    18. Krill, Paul (2020-03-12). "Next.js upgrade emphasizes static site generation". InfoWorld. Retrieved 2020-10-20.
    19. Krill, Paul (July 27, 2020). "Next.js adds incremental static pages regeneration". InfoWorld. Archived from the original on October 2, 2020. Retrieved September 22, 2020. Unknown parameter |url-status= ignored (help)
    20. Krill, Paul (February 14, 2019). "Next.js 8 now supports serverless apps". InfoWorld. Archived from the original on October 2, 2020. Retrieved September 22, 2020. Unknown parameter |url-status= ignored (help)

    External links[edit]


    This article "Next.js" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:Next.js. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.

    Page kept on Wikipedia This page exists already on Wikipedia.