* 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
* fix: improve checking for Rez (fix#994)
Check for Rez in Xcode.app and in command line tools, and error if neither is installed.
* Remove hardcoded paths in favor of xcode-select --print-path
This reverts commit 54784a027c.
I'm not sure that this string substition will work how I want it to.
* Finally...fix issue finding xcode-select tools
* Add tip asking to run xcode-select --install
* Trim tailing whitespace
* add changefile
It is very strict about checking that the deps version specified is published. That means we need to have inter-repo deps already published before we hit this step, and therefore cannot do it as part of the prepublish step.
* 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.
* Fix typo referring to dev path cli arg
The devPath config variable is set to a non-existent command line arg
`argv.p`, it should be `argv.P`
So if the devPath is set via a command line argument, it defaults
to the default value:
```
/home/projects/example2
⟩ yarn tauri init -P http://THISDOESNOTHING
yarn run v1.22.4
$ /home/projects/example2/node_modules/.bin/tauri init -P http://THISDOESNOTHING
[tauri]: running init
? What is your app name? example2
? What should the window title be? Tauri App
? Where are your web assets (HTML/CSS/JS) located, relative to the "<current dir>/src-tauri" folder that will be created? ../dist
dependency:manager Installing missing dependencies... +0ms
dependency:cargo-commands "tauri-bundler" is already installed +18ms
app:spawn [sync] Running "cargo generate-lockfile" +2ms
Updating crates.io index
dependency:crates "tauri" is already installed +941ms
dependency:npm-packages "tauri" is already installed +1s
Done in 6.35s.
/home/projects/example2
⟩ cat ./src-tauri/tauri.conf.json | grep THISDOESNOTHING
/home/projects/example2
```
* Fix similar typo affecting the window title param
* Add change file
* feat(bundler): hide output from bundle_appimage.sh
* fix(bundler/appimage): log file name instead of full path
to match behavior of .deb build
* feat(bundler): hide shell script output unless --verbose is passed
* feat(bundler): add notice about --verbose on error
* fix(bundler): windows fails to compile
* fix(bundler) do not warn about verbosity if verbose is set
* chore(changes) add change file
Co-authored-by: Lucas Nogueira <lucas@tauri.studio>
* inject css with template string to allow for line breaks
alternative solution would to be implement a struct `JsStringLiteral`
with `fmt::Display` that escapes all forbidden codepoints from the spec
https://www.ecma-international.org/ecma-262/#sec-literals-string-literals
template string literal seems fine as all browsers that tauri supports have
had support for them for the past 3-4+ years
Signed-off-by: Chip Reed <chip@chip.sh>
* chore(changes) adjust change file
Co-authored-by: Lucas Nogueira <lucas@tauri.studio>
They can now run check, clippy, fmt, or test. They default to running
clippy, fmt, and test in that order. The cargo sub-commands to run
can be specified as arguments to the script. Only the 4 supported
sub-commands are allowed.
Signed-off-by: Chip Reed <chip@chip.sh>
cat is not available as a command on a default windows install.
This disables the command test that uses cat during tests. It also
disables `test_cmd_fail` even though it passes, because the test
is testing the wrong thing in this case.
