Ryan Glover
Ryan Glover
This could be done via `config.middleware.disabled` where `disabled` is set to an array of strings matching built-in middleware function names.
I think the answer here is _specific_ config, like middleware. If a field that's not supported is defined, warn in the logs. For example: ```javascript joystick.app({ config: { databases: [],...
This should be conditional in the CLI.
This should be a very simple, easy to delete thing like this: ```yaml extends: - eslint:recommended parser: "@babel/eslint-parser" ``` Just add an `.eslintrc.yaml` file to the root and be done...
See: https://www.codeac.io/eslint-config-generator.html
Forgot about this. Would be really helpful for testing in development.
Shouldn't be too hard to do. Just provide a map like this: ```javascript import joystick from '@joystick.js/ui'; joystick.component({ // NOTE: Showing a function example because this could be helpful beyond...
Just make sure to validate the old password and throw an error if it doesn't match.
As for a "why," this would allow Joystick to be used to build embedded apps for things like Raspberry Pi.
Just locate the data at `.joystick/data/sqlite`?