* fix: webpack progress display options not valid
It seems something changed that the progress and display options we were using the hide the output are no longer valid. Remove them.
* add build-release as part of tests
* feat: build tauri communication app on demand
* add run command
* manually set defaults, build tauri.js
* add script defaults and options
* run command doesn't need the `yarn` and `build`
* try just build?
* empty script
* just skip it for now
* try fix on fix/paths-expect-arrays branch
* add tauri as script
* use nested folders
* enable on pr again
* switch to preferGlobal
* skip install
* build without action
* flip global
* list
* add yarn bin to path
* now try with action
* extra spaces
* prepare for release
* don't run on pr
* 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>
* reorder packages that core is published last
* general ledger comment, not just npm
* we do want to create releases
* leading ! does not seem to negate
* dump a bunch of info to debug
* add covector to root
* add workflow to covector config
* bump covector
* add webkit install on publish
* create workflow to version and publish
* remove workflows no longer needed
* add repo info to root package.json
* add early exits based on new output
* switch to dry run version of publish commands
* latest branch is being removed in this PR
* add summary component around yarn audit
* chore: add audit button and yarn audit
This is a new feature that should give us a button that we can click a button to see audit results rather than waiting for a cron or a run within our workflows.
* split audit into js and rust
* perf(workflow) run bundler test only when the bundler changes
* perf(workflow) split clippy/eslint/fmt checks
* chore(workflow) rerun if workflow file change
* chore(workflow) fix name
* fix(tests) bundler test on windows, removed since it's not used
This fixes the commit so it includes "version updates" in the text. As it is a single commit, the default squash behavior uses the commit instead of the PR title for the commit that shows up in the dev branch (which wouldn't trigger the next workflow).
* update readme with notes about character limits and designating bumps
* edit PR template to note addition of a change file
* add change file for #674
* add change file for #673
* add change file for #672
* add change file for #671
* add version action
* set version command in config
* add change file for #677
* add labels to PRs
* Update .changes/tauri-info-crash.md
Co-authored-by: Rajiv Shah <rajivshah1@icloud.com>
* Update .changes/HttpRequestBuilder-implementation.md
Co-authored-by: Rajiv Shah <rajivshah1@icloud.com>
* Update kill-beforeDevProcess-on-shutdown.md
* Update reflect-conf-changes.md
Co-authored-by: Rajiv Shah <rajivshah1@icloud.com>
Co-authored-by: Lucas Fernandes Nogueira <lucasfernandesnog@gmail.com>
We are turning off the smoke tests for the time being as they are eating up our runners to much relative to the value we are currently getting from them. We will enable them in the future in a way that makes better use of our resources.
