20 | 21 | `@feathersjs/authentication` is an abstraction for different authentication mechanisms. It does not handle things like user verification or password reset functionality etc. This can be implemented manually, with the help of libraries like [feathers-authentication-management](https://github.com/feathers-plus/feathers-authentication-management) or a platform like [Auth0](https://auth0.com/). 22 | 23 |24 | -------------------------------------------------------------------------------- /docs/api/databases/adapters.md: -------------------------------------------------------------------------------- 1 | --- 2 | outline: deep 3 | --- 4 | 5 | # Overview 6 | 7 | Feathers database adapters are modules that provide [services](../services.md) that implement standard [CRUD](https://en.wikipedia.org/wiki/Create,_read,_update_and_delete) functionality for a specific database. They use a [common API](./common.md) for initialization and settings, and they provide a [common query syntax](./querying.md). 8 | 9 |
10 | 11 | [Services](../services.md) allow to implement access to _any_ database or API. The database adapters listed here are just convenience wrappers with a common API. See the community adapters section for support for other datastores. 12 | 13 |14 | 15 | ## Core Adapters 16 | 17 | The following data storage adapters are available in Feathers core 18 | 19 | | Core Package | Supported Data Stores | 20 | | -------------------- | -------------------------------------------------------------------------------------------------------------- | 21 | | [Memory](./memory) | Memory | 22 | | [MongoDB](./mongodb) | MongoDB | 23 | | [SQL (Knex)](./knex) | MySQL
6 | Check out the docs to learn more about Feathers.
8 |9 | Feel free say hello on Discord. 10 |
11 |
11 | 4 | Feathers is a full-stack web-framework for creating APIs and real-time applications with TypeScript or JavaScript. 5 |
6 |7 | Feathers can interact with any backend technology, supports many databases out of the box 8 | and works with any frontend technology like React, VueJS, Angular, React Native, 9 | Android or iOS. 10 |
11 |
16 | Build prototypes in minutes and production-ready apps in days.
9 |Seriously.
10 |{{ title }}
15 | 16 |7 | Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh 8 | euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. 9 |
10 | 11 |20 | 21 | For more information on what is available in migration files, see the [Knex migrations documentation](https://knexjs.org/guide/migrations.html). 22 | 23 |24 | -------------------------------------------------------------------------------- /docs/guides/cli/log-error.md: -------------------------------------------------------------------------------- 1 | # Error logging hook 2 | 3 | The `src/hooks/log-error.ts` file exports a `logError` hook that uses the [logger](./logger.md) to log any error for a service method, including validation error details (when they are available). It is registered as an [application hook](./app.md#application-hooks) `all` hook, meaning it will log errors for any service method. 4 | -------------------------------------------------------------------------------- /docs/guides/cli/logger.md: -------------------------------------------------------------------------------- 1 | --- 2 | outline: deep 3 | --- 4 | 5 | # Logging 6 | 7 | ## Logger 8 | 9 | The `src/logger.ts` file initialises the widely used [Winston logger](https://github.com/winstonjs/winston) library, by default with the `info` log level, logging to the console. 10 | 11 | ```ts 12 | import { createLogger, format, transports } from 'winston' 13 | 14 | // Configure the Winston logger. For the complete documentation see https://github.com/winstonjs/winston 15 | export const logger = createLogger({ 16 | // To see more detailed errors, change this to 'debug' 17 | level: 'info', 18 | format: format.combine(format.splat(), format.simple()), 19 | transports: [new transports.Console()] 20 | }) 21 | ``` 22 | 23 | You can import the logger directly in any file where you want to add logging information. 24 | 25 | ```ts 26 | import { logger } from './logger' 27 | 28 | logger.info('Log some information here') 29 | ``` 30 | -------------------------------------------------------------------------------- /docs/guides/cli/package.md: -------------------------------------------------------------------------------- 1 | # package.json 2 | 3 | ## Folders 4 | 5 | The source and test folders to which files are generated is set in the `package.json`. To change them, rename the `src/` or `test/` folder to what you want it to and then update `package.json` `directories` section accordingly: 6 | 7 | ```json 8 | { 9 | "directories": { 10 | "lib": "api/src", 11 | "test": "api/test" 12 | } 13 | } 14 | ``` 15 | -------------------------------------------------------------------------------- /docs/guides/cli/prettierrc.md: -------------------------------------------------------------------------------- 1 | # Prettier 2 | 3 | The Feathers CLI uses [Prettier](https://prettier.io/) for code formatting and generates a configuration for it in a new application. To change the options, like the use of semicolons, quotes etc, edit the `.prettierrc` file with the [options available](https://prettier.io/docs/en/options.html). To update all existing source files with the new code style run 4 | 5 | ``` 6 | npm run prettier 7 | ``` 8 | 9 | When new files are generated, they will use the current Prettier configuration. See the [Prettier Integration with Linters](https://prettier.io/docs/en/integrating-with-linters.html) documentation for how to integrate with tools like ESLint. 10 | -------------------------------------------------------------------------------- /docs/guides/cli/service.shared.md: -------------------------------------------------------------------------------- 1 | --- 2 | outline: deep 3 | --- 4 | 5 | # Service Shared 6 | 7 | The `