Feature: Improve Node.js Roadmap. (#6664)
* In this Commit: --- - Add Semantic versioning in `npm` - Add Node.js Test Runner in `node:test` - What is Testing in `Software Testing` - What is Vitest in `Testing/Vitest` - Few changes in `Working with Databases`. * Add Content in Playwright. * - Fixed Some Spelling Mistakes. - Content Addition - Added Few More Links. *** No deletions or removal. * Add `--watch` Content in Roadmap.fix/discord-link
parent
2ff54205ef
commit
ecda4b6eb3
15 changed files with 106 additions and 14 deletions
@ -1 +1,10 @@ |
||||
# Drizzle |
||||
# Drizzle |
||||
|
||||
Drizzle lets you build your project the way you want, without interfering with your project or structure. Using Drizzle you can define and manage database schemas in TypeScript, access your data in a SQL-like or relational way, and take advantage of opt-in tools to make your developer experience amazing. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Drizzle Website](https://orm.drizzle.team/) |
||||
- [@official@Drizzle Documentation](https://orm.drizzle.team/docs/overview) |
||||
- [@opesource@Drizzle Github](https://github.com/drizzle-team/drizzle-orm) |
||||
- [@article@Getting Started with Drizzle](https://dev.to/franciscomendes10866/getting-started-with-drizzle-orm-a-beginners-tutorial-4782) |
||||
|
@ -1 +1,8 @@ |
||||
# ky |
||||
# Ky |
||||
|
||||
Ky is a tiny and elegant HTTP client based on the browser Fetch API. Ky targets modern browsers and Deno.For older browsers, you will need to transpile and use a fetch polyfill.For Node.js, check out Got.. 1 KB (minified & gzipped), one file, and no dependencies. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@opensource@Ky Official Docs](https://github.com/sindresorhus/ky) |
||||
- [@official@npmjs.org](https://www.npmjs.com/package/ky/v/0.9.0) |
||||
|
@ -1 +1,15 @@ |
||||
# node:test |
||||
# node:test |
||||
|
||||
`node:test` is a built-in module in Node.js that provides a simple, asynchronous test runner. It's designed to make writing tests as straightforward as writing any other code. |
||||
|
||||
## Key Features |
||||
|
||||
- Simplicity: Easy to use and understand. |
||||
- Asynchronous Support: Handles asynchronous code gracefully. |
||||
- Subtests: Allows for organizing tests into hierarchical structures. |
||||
- Hooks: Provides beforeEach and afterEach hooks for setup and teardown. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Test Runner API Docs](https://nodejs.org/api/test.html) |
||||
- [@official@Node.js Test Runner](https://nodejs.org/en/learn/test-runner/using-test-runner) |
||||
|
@ -1 +1,11 @@ |
||||
# Playwright |
||||
# Playwright |
||||
|
||||
Playwright is an open-source automation library developed by Microsoft for testing and automating web applications. 1 It offers a unified API to control Chromium, Firefox, and WebKit browsers, making it a versatile choice for cross-browser testing. |
||||
|
||||
Playwright provides a high-level API to interact with web pages. You can write scripts to simulate user actions, such as clicking buttons, filling forms, and navigating through different pages. Playwright handles the underlying browser interactions, making it easy to write and maintain tests. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Playwright Website](https://playwright.dev/) |
||||
- [@official@Playwright Docs](https://playwright.dev/docs/getting-started-vscode) |
||||
- [@article@Getting Started with Playwright](https://learn.microsoft.com/en-us/shows/getting-started-with-end-to-end-testing-with-playwright/) |
||||
|
@ -1 +1,23 @@ |
||||
# Semantic Versioning |
||||
# Semantic Versioning |
||||
|
||||
Semantic Versioning is a standard for versioning software that's widely adopted in the npm ecosystem. It provides a clear and consistent way to communicate changes in a software package to users. |
||||
|
||||
## Version Format |
||||
|
||||
A semantic version number consists of three parts separated by dots: |
||||
|
||||
- MAJOR: Incremented when there are incompatible API changes. |
||||
- MINOR: Incremented when new functionality is added in a backwards-compatible manner. |
||||
- PATCH: Incremented when bug fixes are made without affecting the API. |
||||
|
||||
### Example: 1.2.3 |
||||
|
||||
- 1 is the major version. |
||||
- 2 is the minor version. |
||||
- 3 is the patch version. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Semver.org](https://semver.org/) |
||||
- [@article@Understanding Semantic Versioning](https://medium.com/codex/understanding-semantic-versioning-a-guide-for-developers-dad5f2b70583) |
||||
- [@article@Devopedia](https://devopedia.org/semantic-versioning) |
@ -1 +1,8 @@ |
||||
# Vitest |
||||
# Vitest |
||||
|
||||
Vitest is a Vite-native unit testing framework that's Jest-compatible. Vitest is a powerful testing library built on top of Vite that is growing in popularity. You can use Vitest for a range of testing needs, such as unit, integration, end-to-end (E2E), snapshot, and performance testing of functions and components. ESM, TypeScript, JSX. Out-of-box ESM, TypeScript and JSX support powered by esbuild. Vitest is free and open source. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Official Website](https://vitest.dev/) |
||||
- [@article@Vitest Documentation](https://vitest.dev/guide/) |
||||
|
@ -1,3 +1,7 @@ |
||||
# What is Database |
||||
|
||||
A database is an organized collection of structured information, or data, typically stored electronically in a computer system. A database is usually controlled by a database management system (DBMS). |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@official@Wikipedia](https://en.wikipedia.org/wiki/Database) |
||||
|
Loading…
Reference in new issue