JavaScript library - Revision history

Citation bot: Added website. Removed parameters. | Use this bot. Report bugs. | Suggested by Neko-chan | #UCB_webform 134/500

2025-03-26T19:51:55Z

Added website. Removed parameters. | Use this bot. Report bugs. | Suggested by Neko-chan | #UCB_webform 134/500

← Previous revision		Revision as of 19:51, 26 March 2025
Line 17:		Line 17:
	[[Lightweight programming language\|Lightweight frameworks]], such as [[Svelte]] and Preact, take different architectural approaches, with Svelte eliminating the virtual DOM entirely in favor of compiling components to efficient JavaScript code, and Preact offering a minimal, compatible alternative to React. Framework choice depends on an application’s requirements, including the team’s expertise, performance goals, and development priorities. <ref name=":0" /><ref name=":1" /><ref name=":2" />		[[Lightweight programming language\|Lightweight frameworks]], such as [[Svelte]] and Preact, take different architectural approaches, with Svelte eliminating the virtual DOM entirely in favor of compiling components to efficient JavaScript code, and Preact offering a minimal, compatible alternative to React. Framework choice depends on an application’s requirements, including the team’s expertise, performance goals, and development priorities. <ref name=":0" /><ref name=":1" /><ref name=":2" />

	A newer category of web frameworks, including enhance.dev, Astro, and Fresh, leverages native web standards while minimizing abstractions and development tooling. <ref>{{Cite web \|title=Enhance \|url=https://github.com/enhance-dev ~~\|url-status=live~~}}</ref><ref>{{Cite web \|title=Astro framework \|url=https://github.com/withastro/astro ~~\|url-status=live~~}}</ref><ref>{{Cite web \|title=Fresh \|url=https://github.com/denoland/fresh ~~\|url-status=live~~}}</ref> These solutions emphasize [[progressive enhancement]], [[server-side rendering]], and optimizing performance. Astro renders static HTML by default while hydrating only interactive parts. Fresh focuses on server-side rendering with zero runtime overhead. Enhance.dev prioritizes progressive enhancement patterns using Web Components. While these tools reduce reliance on client-side JavaScript by shifting logic to build-time or server-side execution, they still use JavaScript where necessary for interactivity. This approach makes them particularly suitable for performance-critical and content-focused applications. <ref name=":0" /><ref name=":1" /><ref name=":2" />		A newer category of web frameworks, including enhance.dev, Astro, and Fresh, leverages native web standards while minimizing abstractions and development tooling. <ref>{{Cite web \|title=Enhance \|website=[[GitHub]] \|url=https://github.com/enhance-dev }}</ref><ref>{{Cite web \|title=Astro framework \|website=[[GitHub]] \|url=https://github.com/withastro/astro }}</ref><ref>{{Cite web \|title=Fresh \|website=[[GitHub]] \|url=https://github.com/denoland/fresh }}</ref> These solutions emphasize [[progressive enhancement]], [[server-side rendering]], and optimizing performance. Astro renders static HTML by default while hydrating only interactive parts. Fresh focuses on server-side rendering with zero runtime overhead. Enhance.dev prioritizes progressive enhancement patterns using Web Components. While these tools reduce reliance on client-side JavaScript by shifting logic to build-time or server-side execution, they still use JavaScript where necessary for interactivity. This approach makes them particularly suitable for performance-critical and content-focused applications. <ref name=":0" /><ref name=":1" /><ref name=":2" />

	== Packages ==		== Packages ==

AdaHephais: Improve presentation and add internal link

2025-03-12T07:09:47Z

Improve presentation and add internal link

← Previous revision		Revision as of 07:09, 12 March 2025
Line 13:		Line 13:
	JavaScript-based web application frameworks, such as [[React (software)\|React]] and [[Vue.js\|Vue]], provide extensive capabilities but come with associated trade-offs. These frameworks often extend or enhance features available through native web technologies, such as [[routing]], [[Component-based software engineering\|component-based development]], and [[state management]]. While native web standards, including Web Components, modern JavaScript APIs like Fetch and ES Modules, and browser capabilities like [[Web Components\|Shadow DOM]], have advanced significantly, frameworks remain widely used for their ability to enhance developer productivity, offer structured [[Pattern\|patterns]] for large-scale applications, simplify handling edge cases, and provide tools for performance optimization. <ref name=":0">{{Cite book \|title=JavaScript Frameworks for Modern Web Development: The Essential Frameworks, Libraries, and Tools to Learn Right Now \|isbn=978-1484249949}}</ref><ref name=":1">{{Cite book \|title=Building Native Web Components: Front-End Development with Polymer and Vue.js \|isbn=978-1484259047}}</ref><ref name=":2">{{Cite book \|title=Hands-On JavaScript High Performance: Build faster web apps using Node.js, Svelte.js, and WebAssembly \|isbn=978-1838821098}}</ref>		JavaScript-based web application frameworks, such as [[React (software)\|React]] and [[Vue.js\|Vue]], provide extensive capabilities but come with associated trade-offs. These frameworks often extend or enhance features available through native web technologies, such as [[routing]], [[Component-based software engineering\|component-based development]], and [[state management]]. While native web standards, including Web Components, modern JavaScript APIs like Fetch and ES Modules, and browser capabilities like [[Web Components\|Shadow DOM]], have advanced significantly, frameworks remain widely used for their ability to enhance developer productivity, offer structured [[Pattern\|patterns]] for large-scale applications, simplify handling edge cases, and provide tools for performance optimization. <ref name=":0">{{Cite book \|title=JavaScript Frameworks for Modern Web Development: The Essential Frameworks, Libraries, and Tools to Learn Right Now \|isbn=978-1484249949}}</ref><ref name=":1">{{Cite book \|title=Building Native Web Components: Front-End Development with Polymer and Vue.js \|isbn=978-1484259047}}</ref><ref name=":2">{{Cite book \|title=Hands-On JavaScript High Performance: Build faster web apps using Node.js, Svelte.js, and WebAssembly \|isbn=978-1838821098}}</ref>

	Frameworks can introduce abstraction layers that may contribute to performance overhead, larger bundle sizes, and increased complexity. Modern frameworks, such as React 18 and Vue 3, address these challenges with features like concurrent rendering, tree-shaking, and selective hydration. While these advancements improve rendering efficiency and resource management, their benefits depend on the specific application and implementation context. Lightweight frameworks, such as Svelte and Preact, take different architectural approaches, with Svelte eliminating the virtual DOM entirely in favor of compiling components to efficient JavaScript code, and Preact offering a minimal, compatible alternative to React. Framework choice depends on an application’s requirements, including the team’s expertise, performance goals, and development priorities. <ref name=":0" /><ref name=":1" /><ref name=":2" />		Frameworks can introduce abstraction layers that may contribute to performance overhead, larger bundle sizes, and increased complexity. Modern frameworks, such as React 18 and Vue 3, address these challenges with features like concurrent rendering, tree-shaking, and selective hydration. While these advancements improve rendering efficiency and resource management, their benefits depend on the specific application and implementation context.

			[[Lightweight programming language\|Lightweight frameworks]], such as [[Svelte]] and Preact, take different architectural approaches, with Svelte eliminating the virtual DOM entirely in favor of compiling components to efficient JavaScript code, and Preact offering a minimal, compatible alternative to React. Framework choice depends on an application’s requirements, including the team’s expertise, performance goals, and development priorities. <ref name=":0" /><ref name=":1" /><ref name=":2" />

	A newer category of web frameworks, including enhance.dev, Astro, and Fresh, leverages native web standards while minimizing abstractions and development tooling. <ref>{{Cite web \|title=Enhance \|url=https://github.com/enhance-dev \|url-status=live}}</ref><ref>{{Cite web \|title=Astro framework \|url=https://github.com/withastro/astro \|url-status=live}}</ref><ref>{{Cite web \|title=Fresh \|url=https://github.com/denoland/fresh \|url-status=live}}</ref> These solutions emphasize [[progressive enhancement]], [[server-side rendering]], and optimizing performance. Astro renders static HTML by default while hydrating only interactive parts. Fresh focuses on server-side rendering with zero runtime overhead. Enhance.dev prioritizes progressive enhancement patterns using Web Components. While these tools reduce reliance on client-side JavaScript by shifting logic to build-time or server-side execution, they still use JavaScript where necessary for interactivity. This approach makes them particularly suitable for performance-critical and content-focused applications. <ref name=":0" /><ref name=":1" /><ref name=":2" />		A newer category of web frameworks, including enhance.dev, Astro, and Fresh, leverages native web standards while minimizing abstractions and development tooling. <ref>{{Cite web \|title=Enhance \|url=https://github.com/enhance-dev \|url-status=live}}</ref><ref>{{Cite web \|title=Astro framework \|url=https://github.com/withastro/astro \|url-status=live}}</ref><ref>{{Cite web \|title=Fresh \|url=https://github.com/denoland/fresh \|url-status=live}}</ref> These solutions emphasize [[progressive enhancement]], [[server-side rendering]], and optimizing performance. Astro renders static HTML by default while hydrating only interactive parts. Fresh focuses on server-side rendering with zero runtime overhead. Enhance.dev prioritizes progressive enhancement patterns using Web Components. While these tools reduce reliance on client-side JavaScript by shifting logic to build-time or server-side execution, they still use JavaScript where necessary for interactivity. This approach makes them particularly suitable for performance-critical and content-focused applications. <ref name=":0" /><ref name=":1" /><ref name=":2" />

AdaHephais: external link

2025-03-12T07:06:18Z

external link

← Previous revision		Revision as of 07:06, 12 March 2025
Line 11:		Line 11:

	=== Capabilities and Trade-offs in Modern Frameworks ===		=== Capabilities and Trade-offs in Modern Frameworks ===
	JavaScript-based web application frameworks, such as [[React (software)\|React]] and [[Vue.js\|Vue]], provide extensive capabilities but come with associated trade-offs. These frameworks often extend or enhance features available through native web technologies, such as [[routing]], [[Component-based software engineering\|component-based development]], and [[state management]]. While native web standards, including Web Components, modern JavaScript APIs like Fetch and ES Modules, and browser capabilities like Shadow DOM, have advanced significantly, frameworks remain widely used for their ability to enhance developer productivity, offer structured patterns for large-scale applications, simplify handling edge cases, and provide tools for performance optimization. <ref name=":0">{{Cite book \|title=JavaScript Frameworks for Modern Web Development: The Essential Frameworks, Libraries, and Tools to Learn Right Now \|isbn=978-1484249949}}</ref><ref name=":1">{{Cite book \|title=Building Native Web Components: Front-End Development with Polymer and Vue.js \|isbn=978-1484259047}}</ref><ref name=":2">{{Cite book \|title=Hands-On JavaScript High Performance: Build faster web apps using Node.js, Svelte.js, and WebAssembly \|isbn=978-1838821098}}</ref>		JavaScript-based web application frameworks, such as [[React (software)\|React]] and [[Vue.js\|Vue]], provide extensive capabilities but come with associated trade-offs. These frameworks often extend or enhance features available through native web technologies, such as [[routing]], [[Component-based software engineering\|component-based development]], and [[state management]]. While native web standards, including Web Components, modern JavaScript APIs like Fetch and ES Modules, and browser capabilities like [[Web Components\|Shadow DOM]], have advanced significantly, frameworks remain widely used for their ability to enhance developer productivity, offer structured [[Pattern\|patterns]] for large-scale applications, simplify handling edge cases, and provide tools for performance optimization. <ref name=":0">{{Cite book \|title=JavaScript Frameworks for Modern Web Development: The Essential Frameworks, Libraries, and Tools to Learn Right Now \|isbn=978-1484249949}}</ref><ref name=":1">{{Cite book \|title=Building Native Web Components: Front-End Development with Polymer and Vue.js \|isbn=978-1484259047}}</ref><ref name=":2">{{Cite book \|title=Hands-On JavaScript High Performance: Build faster web apps using Node.js, Svelte.js, and WebAssembly \|isbn=978-1838821098}}</ref>

	Frameworks can introduce abstraction layers that may contribute to performance overhead, larger bundle sizes, and increased complexity. Modern frameworks, such as React 18 and Vue 3, address these challenges with features like concurrent rendering, tree-shaking, and selective hydration. While these advancements improve rendering efficiency and resource management, their benefits depend on the specific application and implementation context. Lightweight frameworks, such as Svelte and Preact, take different architectural approaches, with Svelte eliminating the virtual DOM entirely in favor of compiling components to efficient JavaScript code, and Preact offering a minimal, compatible alternative to React. Framework choice depends on an application’s requirements, including the team’s expertise, performance goals, and development priorities. <ref name=":0" /><ref name=":1" /><ref name=":2" />		Frameworks can introduce abstraction layers that may contribute to performance overhead, larger bundle sizes, and increased complexity. Modern frameworks, such as React 18 and Vue 3, address these challenges with features like concurrent rendering, tree-shaking, and selective hydration. While these advancements improve rendering efficiency and resource management, their benefits depend on the specific application and implementation context. Lightweight frameworks, such as Svelte and Preact, take different architectural approaches, with Svelte eliminating the virtual DOM entirely in favor of compiling components to efficient JavaScript code, and Preact offering a minimal, compatible alternative to React. Framework choice depends on an application’s requirements, including the team’s expertise, performance goals, and development priorities. <ref name=":0" /><ref name=":1" /><ref name=":2" />

AdaHephais: external link

2025-03-12T07:04:23Z

external link

← Previous revision		Revision as of 07:04, 12 March 2025
Line 11:		Line 11:

	=== Capabilities and Trade-offs in Modern Frameworks ===		=== Capabilities and Trade-offs in Modern Frameworks ===
	JavaScript-based web application frameworks, such as React and Vue, provide extensive capabilities but come with associated trade-offs. These frameworks often extend or enhance features available through native web technologies, such as routing, component-based development, and state management. While native web standards, including Web Components, modern JavaScript APIs like Fetch and ES Modules, and browser capabilities like Shadow DOM, have advanced significantly, frameworks remain widely used for their ability to enhance developer productivity, offer structured patterns for large-scale applications, simplify handling edge cases, and provide tools for performance optimization. <ref name=":0">{{Cite book \|title=JavaScript Frameworks for Modern Web Development: The Essential Frameworks, Libraries, and Tools to Learn Right Now \|isbn=978-1484249949}}</ref><ref name=":1">{{Cite book \|title=Building Native Web Components: Front-End Development with Polymer and Vue.js \|isbn=978-1484259047}}</ref><ref name=":2">{{Cite book \|title=Hands-On JavaScript High Performance: Build faster web apps using Node.js, Svelte.js, and WebAssembly \|isbn=978-1838821098}}</ref>		JavaScript-based web application frameworks, such as [[React (software)\|React]] and [[Vue.js\|Vue]], provide extensive capabilities but come with associated trade-offs. These frameworks often extend or enhance features available through native web technologies, such as [[routing]], [[Component-based software engineering\|component-based development]], and [[state management]]. While native web standards, including Web Components, modern JavaScript APIs like Fetch and ES Modules, and browser capabilities like Shadow DOM, have advanced significantly, frameworks remain widely used for their ability to enhance developer productivity, offer structured patterns for large-scale applications, simplify handling edge cases, and provide tools for performance optimization. <ref name=":0">{{Cite book \|title=JavaScript Frameworks for Modern Web Development: The Essential Frameworks, Libraries, and Tools to Learn Right Now \|isbn=978-1484249949}}</ref><ref name=":1">{{Cite book \|title=Building Native Web Components: Front-End Development with Polymer and Vue.js \|isbn=978-1484259047}}</ref><ref name=":2">{{Cite book \|title=Hands-On JavaScript High Performance: Build faster web apps using Node.js, Svelte.js, and WebAssembly \|isbn=978-1838821098}}</ref>

	Frameworks can introduce abstraction layers that may contribute to performance overhead, larger bundle sizes, and increased complexity. Modern frameworks, such as React 18 and Vue 3, address these challenges with features like concurrent rendering, tree-shaking, and selective hydration. While these advancements improve rendering efficiency and resource management, their benefits depend on the specific application and implementation context. Lightweight frameworks, such as Svelte and Preact, take different architectural approaches, with Svelte eliminating the virtual DOM entirely in favor of compiling components to efficient JavaScript code, and Preact offering a minimal, compatible alternative to React. Framework choice depends on an application’s requirements, including the team’s expertise, performance goals, and development priorities. <ref name=":0" /><ref name=":1" /><ref name=":2" />		Frameworks can introduce abstraction layers that may contribute to performance overhead, larger bundle sizes, and increased complexity. Modern frameworks, such as React 18 and Vue 3, address these challenges with features like concurrent rendering, tree-shaking, and selective hydration. While these advancements improve rendering efficiency and resource management, their benefits depend on the specific application and implementation context. Lightweight frameworks, such as Svelte and Preact, take different architectural approaches, with Svelte eliminating the virtual DOM entirely in favor of compiling components to efficient JavaScript code, and Preact offering a minimal, compatible alternative to React. Framework choice depends on an application’s requirements, including the team’s expertise, performance goals, and development priorities. <ref name=":0" /><ref name=":1" /><ref name=":2" />

Azarboon: /* Frameworks */

2025-01-22T05:38:10Z

Frameworks

← Previous revision		Revision as of 05:38, 22 January 2025
Line 9:		Line 9:
	==Frameworks==		==Frameworks==
	Some JavaScript libraries, such as [[Angular (application platform)\|Angular]], are classified as [[software framework\|frameworks]] since they exhibit full-stack capabilities and properties not found in general JavaScript libraries.<ref>{{Cite web \|date=2019-02-01 \|title=The Difference Between a Framework and a Library \|url=https://www.freecodecamp.org/news/the-difference-between-a-framework-and-a-library-bd133054023f/ \|access-date=2022-03-15 \|website=freeCodeCamp.org \|language=en}}</ref><ref>{{Cite web \|title=What is the difference between Library vs Framework? \|url=https://dev.to/rohitrana/what-is-the-difference-between-library-vs-framework-174n \|access-date=2022-03-15 \|website=DEV Community \|language=en}}</ref>		Some JavaScript libraries, such as [[Angular (application platform)\|Angular]], are classified as [[software framework\|frameworks]] since they exhibit full-stack capabilities and properties not found in general JavaScript libraries.<ref>{{Cite web \|date=2019-02-01 \|title=The Difference Between a Framework and a Library \|url=https://www.freecodecamp.org/news/the-difference-between-a-framework-and-a-library-bd133054023f/ \|access-date=2022-03-15 \|website=freeCodeCamp.org \|language=en}}</ref><ref>{{Cite web \|title=What is the difference between Library vs Framework? \|url=https://dev.to/rohitrana/what-is-the-difference-between-library-vs-framework-174n \|access-date=2022-03-15 \|website=DEV Community \|language=en}}</ref>

			=== Capabilities and Trade-offs in Modern Frameworks ===
			JavaScript-based web application frameworks, such as React and Vue, provide extensive capabilities but come with associated trade-offs. These frameworks often extend or enhance features available through native web technologies, such as routing, component-based development, and state management. While native web standards, including Web Components, modern JavaScript APIs like Fetch and ES Modules, and browser capabilities like Shadow DOM, have advanced significantly, frameworks remain widely used for their ability to enhance developer productivity, offer structured patterns for large-scale applications, simplify handling edge cases, and provide tools for performance optimization. <ref name=":0">{{Cite book \|title=JavaScript Frameworks for Modern Web Development: The Essential Frameworks, Libraries, and Tools to Learn Right Now \|isbn=978-1484249949}}</ref><ref name=":1">{{Cite book \|title=Building Native Web Components: Front-End Development with Polymer and Vue.js \|isbn=978-1484259047}}</ref><ref name=":2">{{Cite book \|title=Hands-On JavaScript High Performance: Build faster web apps using Node.js, Svelte.js, and WebAssembly \|isbn=978-1838821098}}</ref>

			Frameworks can introduce abstraction layers that may contribute to performance overhead, larger bundle sizes, and increased complexity. Modern frameworks, such as React 18 and Vue 3, address these challenges with features like concurrent rendering, tree-shaking, and selective hydration. While these advancements improve rendering efficiency and resource management, their benefits depend on the specific application and implementation context. Lightweight frameworks, such as Svelte and Preact, take different architectural approaches, with Svelte eliminating the virtual DOM entirely in favor of compiling components to efficient JavaScript code, and Preact offering a minimal, compatible alternative to React. Framework choice depends on an application’s requirements, including the team’s expertise, performance goals, and development priorities. <ref name=":0" /><ref name=":1" /><ref name=":2" />

			A newer category of web frameworks, including enhance.dev, Astro, and Fresh, leverages native web standards while minimizing abstractions and development tooling. <ref>{{Cite web \|title=Enhance \|url=https://github.com/enhance-dev \|url-status=live}}</ref><ref>{{Cite web \|title=Astro framework \|url=https://github.com/withastro/astro \|url-status=live}}</ref><ref>{{Cite web \|title=Fresh \|url=https://github.com/denoland/fresh \|url-status=live}}</ref> These solutions emphasize [[progressive enhancement]], [[server-side rendering]], and optimizing performance. Astro renders static HTML by default while hydrating only interactive parts. Fresh focuses on server-side rendering with zero runtime overhead. Enhance.dev prioritizes progressive enhancement patterns using Web Components. While these tools reduce reliance on client-side JavaScript by shifting logic to build-time or server-side execution, they still use JavaScript where necessary for interactivity. This approach makes them particularly suitable for performance-critical and content-focused applications. <ref name=":0" /><ref name=":1" /><ref name=":2" />

	== Packages ==		== Packages ==

Theknightwho: Link to the correct article.

2025-01-12T13:33:52Z

Link to the correct article.

← Previous revision		Revision as of 13:33, 12 January 2025
Line 5:		Line 5:
	With the expanded demands for [[JavaScript]], an easier means for programmers to develop such dynamic interfaces was needed.<ref>{{Cite web \|last=Peters \|first=Siem \|date=2019-04-08 \|title=A Brief History of JavaScript: from Netscape to Frameworks \|url=https://blog.bitsrc.io/a-brief-history-of-javascript-from-netscape-to-frameworks-74bf4774eeef \|access-date=2022-03-15 \|website=Medium \|language=en}}</ref><ref>{{Cite web \|last=AsyncBanana \|date=2021-04-21 \|title=A Short History of JavaScript and Its Evolution \|url=https://javascript.plainenglish.io/a-short-history-of-javascript-and-its-evolution-6f254cc016ee \|access-date=2022-03-15 \|website=Medium \|language=en}}</ref> Thus, JavaScript libraries and JavaScript widget libraries were developed, allowing for developers to concentrate more upon more distinctive applications of [[Ajax_(programming)\|Ajax]].<ref>{{cite book \|url=https://books.google.com/books?id=iILJ_KIyxkgC&pg=PA240 \|title=JavaScript and AJAX For Dummies \|author=Andy Harris \|year=2009 \|isbn=9780470417997 \|publisher=[[Wiley (publisher)\|Wiley]] \|page=240}}</ref> This has led to other companies and groups, such as [[Microsoft]] and [[Yahoo!]] developing their own JavaScript-based user interface libraries, which find their way into the web applications developed by these companies.<ref>{{cite book \|url=https://books.google.com/books?id=owKwLfAll6QC&pg=PR21 \|title=Smashing JQuery \|author=Jake Rutter \|year=2011 \|isbn=9780470977361 \|publisher=[[Wiley (publisher)\|Wiley]] \|page=21}}</ref> Some JavaScript libraries allow for easier integration of JavaScript with other web development technologies, such as [[Cascading Style Sheets\|CSS]], [[PHP]], [[Ruby (programming language)\|Ruby]], and [[Java (programming language)\|Java]], while others provide utilities, often in the form of JavaScript [[JavaScript syntax#Function\|functions]], to make repetitive and complex tasks less taxing.<ref>{{Cite web \|last=Walsh \|first=David \|date=2007-09-05 \|title=6 Reasons To Use JavaScript Libraries & Frameworks \|url=https://davidwalsh.name/6-reasons-to-use-javascript-libraries-frameworks \|access-date=2022-03-15 \|website=David Walsh Blog \|language=en}}</ref><ref>{{Cite web \|title=40 Useful NPM Packages for Node.js Apps in 2021 \|url=https://leanylabs.com/blog/npm-packages-for-nodejs/ \|access-date=2022-03-15 \|website=leanylabs.com \|language=en}}</ref> Many libraries include code to detect differences between runtime environments and remove the need for applications to allow for such inconsistencies.{{Needs citation\|date=March 2022}}		With the expanded demands for [[JavaScript]], an easier means for programmers to develop such dynamic interfaces was needed.<ref>{{Cite web \|last=Peters \|first=Siem \|date=2019-04-08 \|title=A Brief History of JavaScript: from Netscape to Frameworks \|url=https://blog.bitsrc.io/a-brief-history-of-javascript-from-netscape-to-frameworks-74bf4774eeef \|access-date=2022-03-15 \|website=Medium \|language=en}}</ref><ref>{{Cite web \|last=AsyncBanana \|date=2021-04-21 \|title=A Short History of JavaScript and Its Evolution \|url=https://javascript.plainenglish.io/a-short-history-of-javascript-and-its-evolution-6f254cc016ee \|access-date=2022-03-15 \|website=Medium \|language=en}}</ref> Thus, JavaScript libraries and JavaScript widget libraries were developed, allowing for developers to concentrate more upon more distinctive applications of [[Ajax_(programming)\|Ajax]].<ref>{{cite book \|url=https://books.google.com/books?id=iILJ_KIyxkgC&pg=PA240 \|title=JavaScript and AJAX For Dummies \|author=Andy Harris \|year=2009 \|isbn=9780470417997 \|publisher=[[Wiley (publisher)\|Wiley]] \|page=240}}</ref> This has led to other companies and groups, such as [[Microsoft]] and [[Yahoo!]] developing their own JavaScript-based user interface libraries, which find their way into the web applications developed by these companies.<ref>{{cite book \|url=https://books.google.com/books?id=owKwLfAll6QC&pg=PR21 \|title=Smashing JQuery \|author=Jake Rutter \|year=2011 \|isbn=9780470977361 \|publisher=[[Wiley (publisher)\|Wiley]] \|page=21}}</ref> Some JavaScript libraries allow for easier integration of JavaScript with other web development technologies, such as [[Cascading Style Sheets\|CSS]], [[PHP]], [[Ruby (programming language)\|Ruby]], and [[Java (programming language)\|Java]], while others provide utilities, often in the form of JavaScript [[JavaScript syntax#Function\|functions]], to make repetitive and complex tasks less taxing.<ref>{{Cite web \|last=Walsh \|first=David \|date=2007-09-05 \|title=6 Reasons To Use JavaScript Libraries & Frameworks \|url=https://davidwalsh.name/6-reasons-to-use-javascript-libraries-frameworks \|access-date=2022-03-15 \|website=David Walsh Blog \|language=en}}</ref><ref>{{Cite web \|title=40 Useful NPM Packages for Node.js Apps in 2021 \|url=https://leanylabs.com/blog/npm-packages-for-nodejs/ \|access-date=2022-03-15 \|website=leanylabs.com \|language=en}}</ref> Many libraries include code to detect differences between runtime environments and remove the need for applications to allow for such inconsistencies.{{Needs citation\|date=March 2022}}

	Almost all JavaScript libraries are released under either a [[permissive]] or [[copyleft]] license to ensure license-free distribution, usage, and modification.<ref>{{cite book \|url=https://books.google.com/books?id=kW0s1IrlbnIC \|title=JavaScript Cookbook \|author=Shelley Powers \|year=2010 \|pages=389–412 \|isbn=9781449395926 \|publisher=[[O'Reilly Media]]}}</ref>		Almost all JavaScript libraries are released under either a [[Permissive software license\|permissive]] or [[copyleft]] license to ensure license-free distribution, usage, and modification.<ref>{{cite book \|url=https://books.google.com/books?id=kW0s1IrlbnIC \|title=JavaScript Cookbook \|author=Shelley Powers \|year=2010 \|pages=389–412 \|isbn=9781449395926 \|publisher=[[O'Reilly Media]]}}</ref>

	==Frameworks==		==Frameworks==

Superchupu: /* Packages */ npm never stood for "Node Package Manager" and none of the two linked sources state that it ever did. npm's readme itself says its name was never an acronym

2024-09-28T22:51:57Z

Packages: npm never stood for "Node Package Manager" and none of the two linked sources state that it ever did. npm's readme itself says its name was never an acronym

← Previous revision		Revision as of 22:51, 28 September 2024
Line 11:		Line 11:

	== Packages ==		== Packages ==
	All [[Node.js#Package management\|npm packages]] are JavaScript libraries, but not all libraries are packages. Npm ~~originally stood for "Node Package Manager", as the name implies, npm~~ serves as a package manager for packages used in [[Node.js]] runtimes.<ref>{{Cite web \|date=2022-01-20 \|title=A Clear Definition of npm and What it Does \|url=https://css-tricks.com/a-clear-definition-of-npm-and-what-it-does/ \|access-date=2022-03-15 \|website=CSS-Tricks \|language=en}}</ref><ref>{{Cite web \|title=Node.js NPM \|url=https://www.w3schools.com/nodejs/nodejs_npm.asp \|access-date=2022-03-15 \|website=www.w3schools.com \|language=en-US}}</ref> However, some npm packages offer [[Content delivery network\|CDN]] support for use of the library in both Node.js runtimes as well as the browser.<ref>{{Cite web \|last=Grosselle \|first=Alessandro \|date=2019-11-12 \|title=The JS library distribution dilemma, NPM or URL? \|url=https://medium.com/thron-tech/the-js-library-distribution-dilemma-npm-or-url-c63aa5842a4c \|access-date=2022-03-15 \|website=THRON tech blog \|language=en}}</ref>		All [[Node.js#Package management\|npm packages]] are JavaScript libraries, but not all libraries are packages. Npm serves as a package manager for packages used in [[Node.js]] runtimes.<ref>{{Cite web \|date=2022-01-20 \|title=A Clear Definition of npm and What it Does \|url=https://css-tricks.com/a-clear-definition-of-npm-and-what-it-does/ \|access-date=2022-03-15 \|website=CSS-Tricks \|language=en}}</ref><ref>{{Cite web \|title=Node.js NPM \|url=https://www.w3schools.com/nodejs/nodejs_npm.asp \|access-date=2022-03-15 \|website=www.w3schools.com \|language=en-US}}</ref> However, some npm packages offer [[Content delivery network\|CDN]] support for use of the library in both Node.js runtimes as well as the browser.<ref>{{Cite web \|last=Grosselle \|first=Alessandro \|date=2019-11-12 \|title=The JS library distribution dilemma, NPM or URL? \|url=https://medium.com/thron-tech/the-js-library-distribution-dilemma-npm-or-url-c63aa5842a4c \|access-date=2022-03-15 \|website=THRON tech blog \|language=en}}</ref>

	==See also==		==See also==

Jlwoodwa: Reverted good faith edits by JoeNMLC (talk): This is not meant to be a list of particular libraries

2024-09-04T15:24:26Z

Reverted good faith edits by JoeNMLC (talk): This is not meant to be a list of particular libraries

← Previous revision		Revision as of 15:24, 4 September 2024
Line 15:		Line 15:
	==See also==		==See also==
	* [[Ajax framework]]		* [[Ajax framework]]
	* [[GoJS]]
	* [[Widget toolkit]]		* [[Widget toolkit]]
	* [[List of JavaScript libraries]]		* [[List of JavaScript libraries]]

JoeNMLC: /* See also */ ce, add GoJS

2024-09-04T15:19:02Z

LucasBrown: Adding local short description: "Package of JavaScript code", overriding Wikidata description "library of JavaScript code that allows for easier development of JavaScript-based applications"

2024-05-18T10:53:09Z

Adding local short description: "Package of JavaScript code", overriding Wikidata description "library of JavaScript code that allows for easier development of JavaScript-based applications"

← Previous revision		Revision as of 10:53, 18 May 2024
Line 1:		Line 1:
			{{Short description\|Package of JavaScript code}}
	A '''JavaScript library''' is a [[Library (computing)\|library]] of pre-written [[JavaScript]] code that allows for easier development of JavaScript-based applications,<ref>{{cite book \|url=https://books.google.com/books?id=0oWMBAAAQBAJ \|title=JavaScript & JQuery: The Missing Manual \|author=David Sawyer McFarland \|year=2014 \|isbn=9781491948620 \|publisher=[[O'Reilly Media]] \|page=106}}</ref> especially for [[Ajax (programming)\|AJAX]] and other [[World Wide Web\|web-centric]] technologies.<ref>{{Cite web\|url=https://www.khanacademy.org/computing/computer-programming/html-css-js/using-js-libraries-in-your-webpage/a/whats-a-js-library\|title=What is a JS library?\|website=Khan Academy\|access-date=2018-01-15}}</ref> They can be included in a website by embedding it directly in the HTML via a script tag.		A '''JavaScript library''' is a [[Library (computing)\|library]] of pre-written [[JavaScript]] code that allows for easier development of JavaScript-based applications,<ref>{{cite book \|url=https://books.google.com/books?id=0oWMBAAAQBAJ \|title=JavaScript & JQuery: The Missing Manual \|author=David Sawyer McFarland \|year=2014 \|isbn=9781491948620 \|publisher=[[O'Reilly Media]] \|page=106}}</ref> especially for [[Ajax (programming)\|AJAX]] and other [[World Wide Web\|web-centric]] technologies.<ref>{{Cite web\|url=https://www.khanacademy.org/computing/computer-programming/html-css-js/using-js-libraries-in-your-webpage/a/whats-a-js-library\|title=What is a JS library?\|website=Khan Academy\|access-date=2018-01-15}}</ref> They can be included in a website by embedding it directly in the HTML via a script tag.

← Previous revision		Revision as of 15:19, 4 September 2024
Line 15:		Line 15:
	==See also==		==See also==
	* [[Ajax framework]]		* [[Ajax framework]]
			* [[GoJS]]
	* [[Widget toolkit]]		* [[Widget toolkit]]
	* [[List of JavaScript libraries]]		* [[List of JavaScript libraries]]