* chore: add prettier for js/ts formatting
* fix lint-staged to object
* test commit
* format all
* lock file bump
* eslint extends prettier
This will let us skip rules in eslint that prettier can control. Prettier for styles, eslint for code errors.
* add prettier config
* roll back to what we had with eslint settings
* skip mutation observer
* add prettier typescript eslint
* run prettier in lint workflow
* format:check script
* turn off space before function in eslint
it is fighting with prettier
* fix dir in workflow
* remove semis
* add api to eslint
* shift eslint ignore comment after prettier format
* ignore errors that currently exist
* build:typevalidators
* replace was broken on typevalidator build
* try pushing up error
* format
* try removing working dir from eslint workflow
* try node 12
* fix indent in action
* bump eslint
* fix supposeded error and try another
* try breaking eslint
* try building in action
* adjust action paths again
* need dot
* remove build
* fix(tauri.js/eslint): escape glob *
* fix(tauri.js): ignore lint error
* Create prettier-taurijs.md
Co-authored-by: Noah Klayman <noahklayman@gmail.com>
* Create recipes
A recipe consists of:
* Name
* List of NPM dependencies required (dev and production)
* Sub-commands needed
For example, the react recipes run create-react-app to set
up the UI. Future recipes can do anything, they could pull
down a sample UI, clone a repository, download a static HTML
file, initialize another environment that compiles to JS/wasm etc.
The devPath and dist folders nomally configured by the init command
are overridden by the recipe definition.
* Fix no recipe prompts
* Fix linter unsafe assignment error
* Add `beforeXCommand` settings to recipes
This is so good, it makes it possible to just run:
> yarn init
> yarn add tauri
> yarn tauri init # with recipe selected, adds app ui
> yarn tauri dev # starts app ui dev server and rust component
* Rename init to create
Also improve so it exports a function that can be passed
arguments, instead of just reading directly from command line
* Add new tauri init command aliased to create
* Update changes file
* Remove unneeded import
* Add customized splash page for react recipes
* Remove unneeded recipe buildconfig property
* Add no-browser setting to start react dev server
* Revert "Add no-browser setting to start react dev server"
This reverts commit 22bcf3ac5a.
* feat(tauri) extend file system API
* chore(deps) pin web-view deps
* feat(tauri) add path API
* feat(tauri.js) add Dir definition and usage
* fix(tauri) correctly determine app_name
* feat(example) add Dir select to the communication example
* chore(tauri) wrap comment line
* fix(tauri) build works
* feat(tauri.js) improve api module with type defs for each API function
* chore(tauri) move endpoint specific modules
* refactor(tauri) move tcp mod to tauri_api
* feat(tauri) improve readDir signature, API features as kebab-case names
* fix(tauri) make event's payload optional
* feat(tauri) if invoke_handler fails, console.error the error message
* chore(api) improve JSDoc
* chore(tauri.js) update template
* chore(tauri) delete empty mod
* fix(tauri) tests and example with latest API signature
As noted in the comment that was deleted, we should commit the Cargo.lock when creating an executable. This is the template that is copied into the consumer so I think we can safely assume that they will be creating an executable.
Also adding `WixTools` which is created on Windows builds, similar to the `/target/` dir
