@xano/sdk 1.0.12 → 1.0.14
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +28 -0
- package/README.md +36 -36
- package/dist/.build-fingerprint +1 -1
- package/dist/{agent-file-refresh-YM5VRRHE.js → agent-file-refresh-3J6YRVFL.js} +12 -11
- package/dist/{agent-skill-command-GVVCBAGF.js → agent-skill-command-VWDMQWCT.js} +51 -50
- package/dist/{answer-shape-CBUQRSXI.js → answer-shape-AVZSKBR6.js} +4 -4
- package/dist/{backend-dir-NZOLU7TL.js → backend-dir-ISP7RVF2.js} +11 -10
- package/dist/{backend-slot-X5AUX2TT.js → backend-slot-DZAUHLTS.js} +3 -3
- package/dist/bin.js +47 -46
- package/dist/{branch-YS2K3VOB.js → branch-IJTBZZFO.js} +8 -8
- package/dist/{branch-commands-Q46PCVHU.js → branch-commands-75IYFTBS.js} +26 -25
- package/dist/{chunk-EMAFZROF.js → chunk-2FDHIBEU.js} +8 -8
- package/dist/{chunk-CPFWVB3V.js → chunk-2KOB4QPW.js} +13 -13
- package/dist/{chunk-PCHIHVX6.js → chunk-2LF734YB.js} +4 -4
- package/dist/{chunk-R7XZW4SB.js → chunk-3H7R4ISR.js} +2 -2
- package/dist/{chunk-ANBIMJPM.js → chunk-3SZ7QRYA.js} +36 -10
- package/dist/{chunk-DB7P2SSK.js → chunk-45K2QZBR.js} +3 -3
- package/dist/{chunk-C2SAVXAB.js → chunk-4MX5LMPQ.js} +2 -2
- package/dist/{chunk-IZI3SYXH.js → chunk-5FJ4M4HB.js} +38 -38
- package/dist/{chunk-LDSZPRGV.js → chunk-5TWLVFYB.js} +4 -4
- package/dist/{chunk-JKGRQW6D.js → chunk-5W7S2SCA.js} +4 -4
- package/dist/{chunk-F2NFNYCB.js → chunk-6ILHYSLR.js} +3 -3
- package/dist/{chunk-IFXPHVPY.js → chunk-6LJS4M6P.js} +3 -3
- package/dist/{chunk-CTUIMNEM.js → chunk-6X73VFCX.js} +2 -2
- package/dist/{chunk-DZUNF7IH.js → chunk-75QC66XI.js} +2 -2
- package/dist/{chunk-5SZSLAAC.js → chunk-7F3V6CFP.js} +3 -3
- package/dist/{chunk-2PAVJ3QD.js → chunk-B7CPSWQX.js} +7 -7
- package/dist/{chunk-4CS4DKQC.js → chunk-BEKEOXNG.js} +2 -2
- package/dist/{chunk-EC5P4W2D.js → chunk-BSGU4HS6.js} +44 -44
- package/dist/{chunk-U5CTYBAN.js → chunk-CB67GIR3.js} +26 -8
- package/dist/{chunk-M7DIIJPW.js → chunk-DBDTQR23.js} +4 -4
- package/dist/{chunk-5RSPMSSQ.js → chunk-DERQSEB5.js} +9 -9
- package/dist/{chunk-RZABQ4YH.js → chunk-DGYXCIBV.js} +4 -4
- package/dist/{chunk-BXVNRUDB.js → chunk-DLDYQNGP.js} +3 -3
- package/dist/{chunk-I2AVVARA.js → chunk-ECQXASG3.js} +2 -2
- package/dist/{chunk-2BHYGUTI.js → chunk-EQXHUWUO.js} +2 -2
- package/dist/{chunk-ONNSFD73.js → chunk-EYVIUX2T.js} +9 -9
- package/dist/{chunk-JFPLHK6Y.js → chunk-FBSGFPZ4.js} +2 -2
- package/dist/{chunk-EGEANMMK.js → chunk-FIERONKM.js} +2 -2
- package/dist/{chunk-K6BQPFRS.js → chunk-GBSHHNSD.js} +3 -3
- package/dist/{chunk-N3XSXGAL.js → chunk-GCINMMFL.js} +2 -2
- package/dist/{chunk-POZ6V4MU.js → chunk-GKQTXUOW.js} +2 -2
- package/dist/{chunk-HJSAGGHU.js → chunk-GOKRKTCX.js} +3 -3
- package/dist/{chunk-D4VKPOD4.js → chunk-GRXX2TOJ.js} +13 -112
- package/dist/{chunk-YJK4NPXC.js → chunk-GVHWIDEJ.js} +3 -3
- package/dist/{chunk-NZ7ML6LG.js → chunk-HINRE3UM.js} +5 -5
- package/dist/{chunk-OKR66IGL.js → chunk-HK554MDD.js} +7 -7
- package/dist/{chunk-WXLZCBPG.js → chunk-HKI5Y5KW.js} +14 -14
- package/dist/{chunk-HA5Y645X.js → chunk-HMYJOQXT.js} +23 -23
- package/dist/{chunk-DILYWJVP.js → chunk-HXFLHA5K.js} +2 -2
- package/dist/{chunk-A2AOUBJS.js → chunk-IHL2O7VY.js} +2 -2
- package/dist/{chunk-FLDFKG24.js → chunk-IKXXTRMN.js} +4 -4
- package/dist/{chunk-UZ55F3UK.js → chunk-IWJ6GFST.js} +4 -4
- package/dist/{chunk-AMHAGMJM.js → chunk-J3XLCYTQ.js} +80 -80
- package/dist/{chunk-2K2G5TSR.js → chunk-J62TYONQ.js} +3 -3
- package/dist/{chunk-MFEO3EHL.js → chunk-KDEU5FUJ.js} +3 -3
- package/dist/{chunk-VA4JK4TW.js → chunk-KMKUH2IO.js} +3 -3
- package/dist/{chunk-VTMTIBKP.js → chunk-L34DM6QB.js} +2 -2
- package/dist/{chunk-PBIV4DE2.js → chunk-L4WG4BKJ.js} +68 -68
- package/dist/{chunk-7XOQXZ6W.js → chunk-LB76VK6D.js} +7 -7
- package/dist/{chunk-E763QI3G.js → chunk-LJZIBT75.js} +2 -2
- package/dist/{chunk-ETMP7SJ3.js → chunk-LPQZICYN.js} +6 -6
- package/dist/{chunk-UFFIU57H.js → chunk-LSJ3SQEU.js} +4 -4
- package/dist/{chunk-RFB4EXM5.js → chunk-LW7TOIS7.js} +8 -8
- package/dist/{chunk-TOW4EJON.js → chunk-MAXDJZQR.js} +5 -5
- package/dist/{chunk-7NNLRNXE.js → chunk-MIS6F4HM.js} +4 -4
- package/dist/{chunk-WZXEQUIM.js → chunk-MTBKTGZT.js} +2 -2
- package/dist/{chunk-74NRFGL7.js → chunk-MYIIBV6A.js} +5 -5
- package/dist/{chunk-3RZ4UJWV.js → chunk-N6LGLNAC.js} +4 -4
- package/dist/{chunk-H7GMGZHI.js → chunk-NDV6CBR7.js} +2 -2
- package/dist/{chunk-RNVGXJJZ.js → chunk-NOW522B4.js} +13 -13
- package/dist/{chunk-DFCYAEBE.js → chunk-NUZXSIEA.js} +3 -3
- package/dist/{chunk-DYGRTWAI.js → chunk-O44MJTLR.js} +3 -3
- package/dist/{chunk-DH32QXVI.js → chunk-OLQN4Z5R.js} +53 -61
- package/dist/{chunk-2RDZDDPR.js → chunk-P4OWRYE7.js} +28 -28
- package/dist/{chunk-373AVIL2.js → chunk-QAEBBTYR.js} +7 -7
- package/dist/{chunk-6IOBEJWA.js → chunk-QJ25N4W6.js} +4 -4
- package/dist/{chunk-OK7CBTFW.js → chunk-QKHNJ7LE.js} +5 -5
- package/dist/{chunk-3ZVSOZZC.js → chunk-QRMKQYCB.js} +2 -2
- package/dist/{chunk-4GSXWOBS.js → chunk-QX5XQEYB.js} +5 -7
- package/dist/{chunk-4COXXP55.js → chunk-RDZBXTZ3.js} +4 -4
- package/dist/{chunk-U4DSFCH5.js → chunk-RPBB7P4Q.js} +2 -2
- package/dist/{chunk-W5MKVFBQ.js → chunk-RV2BDU7V.js} +5 -5
- package/dist/{chunk-XFQAA2SU.js → chunk-RVAEPPRH.js} +2 -2
- package/dist/{chunk-6QJORUHC.js → chunk-RYWNNJK5.js} +2 -2
- package/dist/{chunk-JPAUQ7MK.js → chunk-SAEIVQLP.js} +3 -3
- package/dist/{chunk-H5FAYLCR.js → chunk-SPLRKCFV.js} +2 -2
- package/dist/{chunk-3XZ44H2E.js → chunk-SUKO4SZG.js} +63 -55
- package/dist/{chunk-B5N6EWOM.js → chunk-UQ2OD7D4.js} +3 -3
- package/dist/{chunk-G3A3XKCS.js → chunk-VBSCWV5H.js} +49 -49
- package/dist/chunk-VYJYDMY6.js +9 -0
- package/dist/{chunk-C4TZP5PQ.js → chunk-WS2X5BB2.js} +5 -5
- package/dist/{chunk-P5JF3U65.js → chunk-WS4BA75E.js} +37 -4
- package/dist/{chunk-SAYHY2N3.js → chunk-XCFQLP6G.js} +8 -8
- package/dist/{chunk-OCNTMJSY.js → chunk-XPSDDTUZ.js} +3 -3
- package/dist/{chunk-OBRMA2VK.js → chunk-XY4OBD26.js} +3 -3
- package/dist/{chunk-XVOODRNK.js → chunk-Y5XAPLZS.js} +4 -4
- package/dist/{chunk-WQNN6WLB.js → chunk-YFQCDLCQ.js} +14 -14
- package/dist/{chunk-SAKWZG5I.js → chunk-YL3WVBR5.js} +9 -9
- package/dist/{chunk-XM56DAM7.js → chunk-YR3MNGWZ.js} +8 -8
- package/dist/{chunk-HUEFVPYW.js → chunk-YTQYP7UJ.js} +3 -3
- package/dist/{chunk-KICERNAP.js → chunk-Z3DQ7ULY.js} +4 -4
- package/dist/{chunk-JHQAVWHW.js → chunk-Z4BQPABS.js} +2 -2
- package/dist/{chunk-6LECAG3Y.js → chunk-ZMJRAMLA.js} +4 -4
- package/dist/{chunk-AUYXBKGR.js → chunk-ZOHEHIFS.js} +2 -2
- package/dist/{chunk-A3CT26GX.js → chunk-ZRXDPCMN.js} +2 -2
- package/dist/cli.js +45 -44
- package/dist/{codegen-command-H3HO7UFA.js → codegen-command-JWOW6HE5.js} +63 -62
- package/dist/codegen.js +2 -2
- package/dist/{commands-IFRAGWGK.js → commands-5ILSWDSV.js} +2 -2
- package/dist/{completion-RTXCODHS.js → completion-UNKBVVDT.js} +2 -2
- package/dist/{config-EHFXNFSP.js → config-NTOASFCA.js} +3 -3
- package/dist/{deploy-command-7PWQJ4VV.js → deploy-command-WESYWFJN.js} +52 -51
- package/dist/{deploy-source-CJHEVGOS.js → deploy-source-ZQQNMDFX.js} +27 -26
- package/dist/{dev-env-sync-VVLYQUPR.js → dev-env-sync-4XJT7WOT.js} +46 -45
- package/dist/{display-name-hint-BKPMISQU.js → display-name-hint-MYXCCAOP.js} +10 -10
- package/dist/{env-example-refresh-GLFC2FTE.js → env-example-refresh-4V2OCDJE.js} +64 -63
- package/dist/{env-pull-command-OY3SXNJC.js → env-pull-command-SK5FS477.js} +42 -41
- package/dist/{env-target-PDDDAA5I.js → env-target-TEFSYACA.js} +9 -9
- package/dist/{env-var-command-UTYDJN24.js → env-var-command-IJHKA2WJ.js} +37 -36
- package/dist/{ephemeral-CART6DIR.js → ephemeral-VLPRDNEJ.js} +8 -8
- package/dist/{ephemeral-command-ALIHUF7G.js → ephemeral-command-WCO5J4SN.js} +43 -42
- package/dist/{ephemeral-state-HPKSKC4Y.js → ephemeral-state-RUOU2GFS.js} +7 -7
- package/dist/{generate-command-S37XFYPD.js → generate-command-3WCOUOEQ.js} +68 -67
- package/dist/{gitignore-DKDWGWPS.js → gitignore-WYS3GMOX.js} +15 -14
- package/dist/{guards-RU4C7TFG.js → guards-PPIBIMFZ.js} +6 -6
- package/dist/{impersonate-command-HPCSKJAV.js → impersonate-command-UMYVQTCG.js} +33 -32
- package/dist/{import-RUBCGLCA.js → import-T4ZTOTBT.js} +4 -4
- package/dist/index.js +11 -11
- package/dist/{init-command-RWXBXJPG.js → init-command-UR5MSXIH.js} +50 -51
- package/dist/{init-modules-LFLW2PQC.js → init-modules-7KALFI5C.js} +7 -7
- package/dist/{init-web-OGKACAOC.js → init-web-DYE2FEXL.js} +2 -2
- package/dist/internal.js +72 -66
- package/dist/{keep-data-merge-7JGGZKDM.js → keep-data-merge-OVHCIEBG.js} +24 -24
- package/dist/{lambda-config-reconcile-FXPDH2U5.js → lambda-config-reconcile-VOBVZPWS.js} +3 -3
- package/dist/{landing-record-QJV7KNS4.js → landing-record-AIHNW4AZ.js} +17 -16
- package/dist/{live-diff-HARRGFV4.js → live-diff-UMSOGPX3.js} +6 -6
- package/dist/{local-engine-choice-NNSHE5FO.js → local-engine-choice-XDGTATKJ.js} +30 -29
- package/dist/{local-engine-command-UGIZ4UO6.js → local-engine-command-VQWNQ7UK.js} +35 -34
- package/dist/{local-engine-deploy-ZZVHBI2X.js → local-engine-deploy-4N4NFZ4T.js} +11 -11
- package/dist/{local-engine-lookup-QFRKO35F.js → local-engine-lookup-AQTUGSBT.js} +2 -2
- package/dist/{local-engine-mcp-bridge-T2EFRRAF.js → local-engine-mcp-bridge-AMYRH4SY.js} +9 -9
- package/dist/{local-engine-mcp-command-YUSZC7MF.js → local-engine-mcp-command-AIMNMXQG.js} +41 -48
- package/dist/{local-engine-process-XH35DURU.js → local-engine-process-OD5OSWDG.js} +6 -6
- package/dist/{local-engine-update-check-HAXE7BVG.js → local-engine-update-check-G3YCBXRE.js} +4 -4
- package/dist/{lock-commands-VT4R2DEE.js → lock-commands-H3YV2D6M.js} +50 -49
- package/dist/{login-command-4D3KPQUY.js → login-command-NMM3JNDZ.js} +23 -22
- package/dist/{logout-command-ALKHCJKS.js → logout-command-7DYC6G32.js} +13 -12
- package/dist/{loop-QHZD37KX.js → loop-DJNIHC7O.js} +6 -6
- package/dist/{marketplace-command-64TE2NGV.js → marketplace-command-UCSHDZGO.js} +33 -33
- package/dist/{marketplace-resolve-HPCRNV5O.js → marketplace-resolve-JR4BBJ6K.js} +5 -5
- package/dist/{meta-client-7MLLUZB4.js → meta-client-CD3TXQP6.js} +10 -10
- package/dist/{module-manifest-EFE6JBZW.js → module-manifest-63I5GRK4.js} +3 -3
- package/dist/node.js +50 -49
- package/dist/{operation-outcome-TYAOVNOM.js → operation-outcome-2ONIIDRU.js} +19 -19
- package/dist/{output-target-63ECBUX2.js → output-target-67LHZKCO.js} +16 -15
- package/dist/{plan-disclosure-WEMB5ZJ2.js → plan-disclosure-T7DF4SRJ.js} +16 -16
- package/dist/{plugin-contributions-U5PAZKBE.js → plugin-contributions-YYEP7IWH.js} +4 -4
- package/dist/{plugin-prompt-O5PAMV5B.js → plugin-prompt-GKCQKNYI.js} +4 -4
- package/dist/{plugin-questions-ZVYNKDRB.js → plugin-questions-P7MA3TYI.js} +3 -3
- package/dist/plugin.d.ts +2 -1
- package/dist/{preflight-command-OUVAX5IJ.js → preflight-command-TJ7FURXB.js} +56 -55
- package/dist/{profile-command-NUO5U2HQ.js → profile-command-LDPLTJEJ.js} +24 -23
- package/dist/{profile-pointer-VTOZDBHM.js → profile-pointer-JJ7K5O2R.js} +3 -3
- package/dist/{project-dependency-EZNTHMWI.js → project-dependency-X3KCWBK5.js} +6 -6
- package/dist/{project-sdk-ZGJM4WYQ.js → project-sdk-YHJZRCNB.js} +3 -3
- package/dist/promote-command-RURHOLNR.js +148 -0
- package/dist/{prompt-F7UVH4GP.js → prompt-QNMJIWNI.js} +3 -3
- package/dist/{publish-command-KVGNFBSU.js → publish-command-IIRN6NWN.js} +55 -54
- package/dist/{pull-command-OVXIMVUB.js → pull-command-ITO76ENU.js} +66 -65
- package/dist/{pull-superseded-77UZ7CHH.js → pull-superseded-6HADGGC5.js} +3 -3
- package/dist/{release-command-E54WUJKB.js → release-command-CVGIUD4M.js} +60 -59
- package/dist/{release-ns-command-SLRL3O3W.js → release-ns-command-YLCQPVH3.js} +78 -77
- package/dist/{retry-command-S5QALD5Z.js → retry-command-LFZYEVRU.js} +7 -7
- package/dist/{routes-manifest-ET2TTSCL.js → routes-manifest-R3TQRB24.js} +6 -6
- package/dist/{routes-manifest-file-IX4TOZCO.js → routes-manifest-file-GYNYFKAH.js} +9 -9
- package/dist/scaffold.d.ts +0 -5
- package/dist/scaffold.js +2 -2
- package/dist/{secrets-file-4NQWGCJG.js → secrets-file-PCNAFXNV.js} +15 -14
- package/dist/{secrets-fill-command-5NNHSYFX.js → secrets-fill-command-G7NQMRXU.js} +49 -48
- package/dist/{seed-5YLQRT2D.js → seed-4CD55LB4.js} +6 -6
- package/dist/{source-resolve-HSJSVKUC.js → source-resolve-U4SJR7ZA.js} +17 -17
- package/dist/{static-host-TQP3FXPI.js → static-host-MO4VDHL7.js} +4 -4
- package/dist/{status-command-UFIMW7SZ.js → status-command-CD72PXIT.js} +60 -34
- package/dist/{store-ZE5BXCOW.js → store-AJX4MC7Y.js} +5 -5
- package/dist/{sync-baseline-JGAAOS25.js → sync-baseline-BJDKG4F2.js} +7 -7
- package/dist/{sync-contributions-35ZAYBUH.js → sync-contributions-XK6LHISZ.js} +8 -8
- package/dist/{sync-record-ILWS44DG.js → sync-record-NE62ERA3.js} +9 -9
- package/dist/{table-V3LTQUY6.js → table-WPRAM4VW.js} +8 -8
- package/dist/{tables-command-TISOU6DR.js → tables-command-NMTKR52H.js} +35 -34
- package/dist/{tenant-7WUS7Q6V.js → tenant-IIYECNWO.js} +9 -9
- package/dist/{tenant-command-ITCPN43T.js → tenant-command-XQAWT46C.js} +83 -82
- package/dist/{test-command-7SFAJ6HX.js → test-command-W4AD4KT4.js} +32 -31
- package/dist/{tests-ENFUACKD.js → tests-JWQRHFCT.js} +5 -5
- package/dist/{token-OXGOA6WE.js → token-P3VQ6ITJ.js} +9 -8
- package/dist/{toolchain-hooks-QIFGPGH2.js → toolchain-hooks-UAJBPSTC.js} +8 -8
- package/dist/{toolchain-modules-Q3Z6APPF.js → toolchain-modules-S3MPHCUI.js} +4 -4
- package/dist/{toolchain-peers-K44IINPG.js → toolchain-peers-FQJBTKEB.js} +7 -7
- package/dist/{tracked-backend-IYTIZZYV.js → tracked-backend-WWEPNUD5.js} +30 -29
- package/dist/{update-check-LSCQRDRR.js → update-check-O7QC5TBB.js} +48 -47
- package/dist/{upgrade-command-RQEQJO5Y.js → upgrade-command-J6LRNHYF.js} +51 -50
- package/dist/{whoami-command-NT3FVBZM.js → whoami-command-KWRP2CII.js} +12 -11
- package/dist/{workspace-5RHOJC7K.js → workspace-3YNK4XO4.js} +4 -4
- package/dist/{workspace-binding-YUU6KB53.js → workspace-binding-TTDNXHO5.js} +11 -10
- package/dist/{workspace-command-QSJHX5RS.js → workspace-command-W4ANGLCZ.js} +79 -78
- package/dist/{workspace-env-M7RYVJB3.js → workspace-env-6LJGCTZA.js} +12 -11
- package/dist/{workspace-export-GHMUSX2P.js → workspace-export-PUEXKZNS.js} +4 -4
- package/dist/{writable-Y6CE2CGK.js → writable-LMMG4AFZ.js} +3 -3
- package/dist/{xano-2A2GT7EH.js → xano-Z3SRHYOR.js} +7 -7
- package/dist/{xanosdk-import-4TLNYFKC.js → xanosdk-import-PNNMZ4SF.js} +5 -5
- package/dist/{xanosdk-project-4NH6332J.js → xanosdk-project-YW3BQY2E.js} +13 -12
- package/guides/README.md +3 -3
- package/guides/authoring.md +24 -18
- package/guides/bundle.md +2 -2
- package/guides/cli.md +204 -191
- package/guides/codegen.md +20 -19
- package/guides/codes.md +3 -3
- package/guides/coverage.md +5 -4
- package/guides/deploying.md +140 -133
- package/guides/environment.md +38 -38
- package/guides/marketplace.md +35 -29
- package/guides/module-contract.md +20 -15
- package/guides/object-kinds.md +12 -9
- package/guides/project-structure.md +4 -4
- package/guides/scaffold.md +44 -32
- package/guides/typed-frontend.md +10 -9
- package/llms/client.md +4 -4
- package/llms/errors.md +2 -2
- package/llms/fields.md +1 -1
- package/llms/kinds-agent-mcp.md +1 -1
- package/llms/kinds-knowledge.md +2 -2
- package/llms/kinds-realtime.md +2 -2
- package/llms/lock.md +3 -3
- package/llms/object-kinds.md +2 -2
- package/llms/statements-calls.md +1 -1
- package/llms/statements-runtime.md +2 -2
- package/llms/tests.md +3 -3
- package/llms/toolchain.md +2 -2
- package/llms-full.txt +61 -58
- package/llms.txt +36 -33
- package/manifest.json +2 -2
- package/package.json +1 -1
- package/skills/xano-backend/SKILL.md +7 -7
- package/dist/promote-command-MGLAYQDY.js +0 -147
package/guides/environment.md
CHANGED
|
@@ -15,21 +15,21 @@ are what you get when the variable is unset.
|
|
|
15
15
|
| `XANO_WORKSPACE_ID` | Numeric workspace the meta credential acts on. |
|
|
16
16
|
| `XANO_META_TOKEN` | Meta API bearer token. With the two above it forms a complete credential that outranks every other source, reads no file, and never rotates. |
|
|
17
17
|
| `XANO_REFRESH_TOKEN` | OAuth refresh token for non-interactive runs (CI, agents). Paired with `XANO_CLIENT_ID`; the target instance comes from the token's own `aud` claim. Rotates on use — prefer the meta credential above. |
|
|
18
|
-
| `XANO_CLIENT_ID` | OAuth client id that goes with `XANO_REFRESH_TOKEN`. Both are copied once out of the profile in `auth.json` after a local `
|
|
18
|
+
| `XANO_CLIENT_ID` | OAuth client id that goes with `XANO_REFRESH_TOKEN`. Both are copied once out of the profile in `auth.json` after a local `npx @xano/sdk login`. |
|
|
19
19
|
| `XANO_CONFIG` | Explicit path to the credential file. Wins over both default locations — the same thing `--config <path>` does. Refused beside `--local-auth`, which names a different file. |
|
|
20
20
|
| `XANO_PROFILE` | Which stored credential profile to act as, when no `--profile` names one. Outranked by the flag, by the project's `xano.profile.json` pin, and by an environment credential (which displaces it with a note on stderr). |
|
|
21
21
|
| `XANO_GLOBAL_CONFIG` | Moves the **shared** credential cache off `~/.xanosdk/auth.json`. Only changes where the global cache lives; the project-local `./.xano/auth.json` and the `XANO_CONFIG`/`--config` override are unaffected. |
|
|
22
22
|
| `XANO_CLIENT_FILE` | Moves the OAuth **client-registration** cache off `~/.xano/xanosdk-clients.json`. That file holds the `client_id` minted per auth host + redirect URI, not a credential. |
|
|
23
23
|
| `XANO_ORIGIN` | OAuth host to sign in against, instead of the default — the same thing `--origin` does. An origin only (`https://host`): a path, query or fragment is refused. |
|
|
24
|
-
| `XANO_NO_BROWSER` | Set to anything non-empty and `
|
|
24
|
+
| `XANO_NO_BROWSER` | Set to anything non-empty and `npx @xano/sdk login` will **not** launch a browser; it prints the authorize URL to stderr for you to open yourself. The loopback server still runs and still waits for the redirect, so the flow completes only if the browser you open it in can reach this machine's `127.0.0.1`. For a machine that has no browser to launch. When the browser is on a **different** machine, that redirect cannot arrive — use `npx @xano/sdk login --paste` instead. |
|
|
25
25
|
|
|
26
|
-
**`
|
|
26
|
+
**`npx @xano/sdk preflight`** — an optional override target. With none of these set, `preflight` uses the stored login credential and creates its ephemeral under the workspace that credential pins
|
|
27
27
|
|
|
28
28
|
| Variable | What it does |
|
|
29
29
|
|---|---|
|
|
30
|
-
| `XANO_VALIDATE_INSTANCE` | Base URL of the instance to validate against (`https://your-instance.xano.io`, or `http://localhost:8080` for local Docker).
|
|
31
|
-
| `XANO_VALIDATE_TOKEN` | Meta API bearer token for that instance. Required. |
|
|
32
|
-
| `XANO_VALIDATE_WORKSPACE_ID` | Parent workspace the run's throwaway environment is created under. Defaults to `1`. |
|
|
30
|
+
| `XANO_VALIDATE_INSTANCE` | Base URL of the instance to validate against (`https://your-instance.xano.io`, or `http://localhost:8080` for local Docker). Optional; when any `XANO_VALIDATE_*` is set (or `--instance <url>`, which overrides it) the pair takes over from the login, and both must then be present. |
|
|
31
|
+
| `XANO_VALIDATE_TOKEN` | Meta API bearer token for that instance. Required once the override is in use. |
|
|
32
|
+
| `XANO_VALIDATE_WORKSPACE_ID` | Parent workspace the run's throwaway environment is created under, when the override is in use. Defaults to `1`. |
|
|
33
33
|
|
|
34
34
|
**Output & diagnostics**
|
|
35
35
|
|
|
@@ -45,7 +45,7 @@ are what you get when the variable is unset.
|
|
|
45
45
|
|---|---|
|
|
46
46
|
| `XANOSDK_NO_UPDATE_CHECK` | Turns the "a newer version is out" notice off (it reads the registry at most once an hour). |
|
|
47
47
|
| `NO_UPDATE_NOTIFIER` | The de-facto convention, honored identically. `CI` being set also silences the notice. |
|
|
48
|
-
| `XANOSDK_INSTALL_MODE` | `global` or `local` — pins whether the notice suggests `npm i -g` or `
|
|
48
|
+
| `XANOSDK_INSTALL_MODE` | `global` or `local` — pins whether the notice suggests `npm i -g` or `npx @xano/sdk upgrade` (a project-local install), instead of detecting it. |
|
|
49
49
|
| `XANOSDK_UPDATE_REGISTRY` | Registry URL the check reads, instead of the npm endpoint for `@xano/sdk`. |
|
|
50
50
|
| `XANOSDK_UPDATE_CACHE` | Moves the check's cache file off `~/.xanosdk/update-check.json`. |
|
|
51
51
|
|
|
@@ -56,13 +56,13 @@ are what you get when the variable is unset.
|
|
|
56
56
|
| `XANOSDK_ENGINE_OVERRIDE` | An engine to run instead of the project's pinned one, for every `deploy --local` in this shell: a version (`v0.1.8`), an `https://` URL to an engine archive (plain `http://` only from this machine), or an archive path. A value on `--local=` beats it; it never reads or moves the pin. |
|
|
57
57
|
| `XANOSDK_ENGINE_TOKEN` | Bearer credential sent with an override URL's download — only to that URL's own origin, never to another host a redirect leads to. |
|
|
58
58
|
| `XANOSDK_ENGINE_HOME` | Moves everything the Xano Engine writes off `~/.xanosdk/local-engine`: the engine cache, the running-engine records, and the engine's own logs and runtime data — see [where the engine keeps its data](deploying.md#where-the-engine-keeps-its-data). |
|
|
59
|
-
| `XANOSDK_ENGINE_RELEASES_URL` | A different engine release service for version lookups. Its engines are fetched fresh each deploy, the pin is not read or written, and `
|
|
59
|
+
| `XANOSDK_ENGINE_RELEASES_URL` | A different engine release service for version lookups. Its engines are fetched fresh each deploy, the pin is not read or written, and `npx @xano/sdk local update` refuses while it is set. |
|
|
60
60
|
|
|
61
61
|
**Escape hatches**
|
|
62
62
|
|
|
63
63
|
| Variable | What it does |
|
|
64
64
|
|---|---|
|
|
65
|
-
| `XANOSDK_MARKETPLACE_URL` | Base URL the `
|
|
65
|
+
| `XANOSDK_MARKETPLACE_URL` | Base URL the `npx @xano/sdk marketplace` reads hit, instead of the published catalogue. Repoints the three read verbs without waiting for a release. A path is kept, so `https://<instance>/tenant/<name>` works. |
|
|
66
66
|
| `XANOSDK_PROVE_DIFF` | A file path. Codegen appends one JSON line per statement that fell back to `raw()` — the arm that declined and the key paths where the re-encode disagreed. The decline *reason* is on the report either way; this adds the machine-readable detail. |
|
|
67
67
|
|
|
68
68
|
> `process.env` read inside a **workspace definition** is a different thing entirely: it
|
|
@@ -95,7 +95,7 @@ checked-out project never holds a secret it did not fetch on purpose.
|
|
|
95
95
|
|
|
96
96
|
| Path | What it is |
|
|
97
97
|
|---|---|
|
|
98
|
-
| `xano/.env` | Where the values live. Gitignored by the scaffold, and preserved across a `
|
|
98
|
+
| `xano/.env` | Where the values live. Gitignored by the scaffold, and preserved across a `npx @xano/sdk pull` rather than rewritten. Read with no flag by the commands that compile a bundle: `deploy`, `export`, `preflight`, and `release create`, whose convergence comparison compiles the entry unless `--bundle` names one. |
|
|
99
99
|
| `xano/.env.example` | Generated beside it, listing the declared names as commented lines. Committed. Copy it to `xano/.env` on a fresh clone and fill in the values. The lines stay commented on purpose, so an unedited copy meets the refusal below rather than sending empty strings to your backend. |
|
|
100
100
|
|
|
101
101
|
`xano/` is the scaffold's backend directory. The file is read from the directory of the
|
|
@@ -107,9 +107,9 @@ it looked for.
|
|
|
107
107
|
**Filling it**
|
|
108
108
|
|
|
109
109
|
```bash
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
|
|
110
|
+
npx @xano/sdk env pull # fetch the values from the source this project last deployed to
|
|
111
|
+
npx @xano/sdk env pull --from tenant:prod # name the source explicitly
|
|
112
|
+
npx @xano/sdk env pull --from workspace --yes # and skip the confirmation
|
|
113
113
|
```
|
|
114
114
|
|
|
115
115
|
The source is a backend that is running: `workspace`, `ephemeral[:<name>]`,
|
|
@@ -131,9 +131,9 @@ resolved env values in cleartext (see the `--bundle` note below).
|
|
|
131
131
|
**Changing one value on a running backend**
|
|
132
132
|
|
|
133
133
|
```bash
|
|
134
|
-
printf %s "$STRIPE_KEY" |
|
|
135
|
-
|
|
136
|
-
|
|
134
|
+
printf %s "$STRIPE_KEY" | npx @xano/sdk env set STRIPE_KEY --to workspace --yes # value on stdin
|
|
135
|
+
npx @xano/sdk env set FEATURE_FLAG on --to local # or as the second argument
|
|
136
|
+
npx @xano/sdk env unset STRIPE_KEY --to tenant:prod-eu # remove it
|
|
137
137
|
```
|
|
138
138
|
|
|
139
139
|
`env set` creates the variable or replaces its value, and `env unset` removes it. Every other
|
|
@@ -165,7 +165,7 @@ update it too if the change should outlive the next deploy.
|
|
|
165
165
|
| `--env-var KEY=VALUE` | One value, for this process only. Never written to `xano/.env`, never printed back. Repeatable. Highest precedence: it beats whichever file supplied values, the default `xano/.env` or an explicit `--backend-env-file`. On `export` the value is still compiled into the bundle that command writes. A secret on the command line also lands in shell history and the process table, so prefer `--backend-env-file` in CI. |
|
|
166
166
|
| `--backend-env-file <path>` | Read values from this dotenv-style file **instead of** `xano/.env`. It replaces the default rather than layering over it, so pointing at a CI secret mount cannot also ship a developer's local file. The flip side: a name that only `xano/.env` had is now unsupplied. |
|
|
167
167
|
| `--allow-empty-env=NAME[,NAME]` | Send these declared names empty on purpose, **clearing whatever the target holds for them**. Per-name only; there is deliberately no bare form. |
|
|
168
|
-
| `--allow-empty-doc-token
|
|
168
|
+
| `--allow-empty-doc-token=<scope>` | The same, for a documentation token — but it **opens** something: the target's doc-site gate is cleared and those docs become publicly readable. The scope is `workspace` or an API group's name; it is not comma-split, so repeat the flag for more than one. No bare form. |
|
|
169
169
|
|
|
170
170
|
**A deploy replaces the workspace's env set.** So a declared name left empty in the config
|
|
171
171
|
that no file and no flag supplies would clear the live value, and `deploy` refuses instead,
|
|
@@ -179,7 +179,7 @@ and is not refused — unless `--keep-data` cannot keep that environment's data
|
|
|
179
179
|
replaces it after all. A `deploy --to` without `--replace` merges the same add-only way, and it
|
|
180
180
|
still refuses: a name the target does not hold would be created there with no value, on a
|
|
181
181
|
backend someone keeps. A `--dry-run` sends nothing, so it reports the refusal the real deploy
|
|
182
|
-
would make as a warning and prints its plan. `
|
|
182
|
+
would make as a warning and prints its plan. `npx @xano/sdk env pull` warns about each declared name
|
|
183
183
|
the backend holds no value for, since the file it writes has none for it either.
|
|
184
184
|
|
|
185
185
|
**The refusal only covers declared names.** A variable that exists in the backend but is not
|
|
@@ -189,7 +189,7 @@ routes reach that state: someone adds a variable in the backend after your last
|
|
|
189
189
|
swapping `xano/.env` for an `--backend-env-file` that holds only the declared names. So declare every
|
|
190
190
|
name the stack reads, and carry the rest across when you swap files.
|
|
191
191
|
|
|
192
|
-
The refusal is part of the **compile**, so `
|
|
192
|
+
The refusal is part of the **compile**, so `npx @xano/sdk deploy --bundle <path>` does not get it. A
|
|
193
193
|
pre-built bundle carries whatever env it was built with and sends exactly that, so a
|
|
194
194
|
build-once-deploy-the-artifact pipeline resolves its values at build time: pass
|
|
195
195
|
`--backend-env-file`/`--env-var` to the `export` that produces the bundle. Two consequences worth
|
|
@@ -213,18 +213,18 @@ identity, and a dotenv file is the right shape. A documentation token is address
|
|
|
213
213
|
**object** that holds it: this workspace, that API group. It has no name of its own, so it is
|
|
214
214
|
stored under that object's identity instead, and `env(...)` cannot read it from anywhere.
|
|
215
215
|
|
|
216
|
-
That file is SDK-owned. `
|
|
216
|
+
That file is SDK-owned. `npx @xano/sdk pull` writes it and every build reads it back, so a pull
|
|
217
217
|
followed by a deploy restores the gate with no manual step — which is the whole reason it
|
|
218
218
|
exists. Nobody edits it by hand; `--no-secrets` on a pull finds the tokens and writes none, for
|
|
219
219
|
a machine where a secret on disk is not wanted.
|
|
220
220
|
|
|
221
221
|
A pull only answers for an object that already HAS a token. A gate you declare in source — a new
|
|
222
222
|
API group, or a doc site you decided to close — has none to fetch, and that is what
|
|
223
|
-
`
|
|
223
|
+
`npx @xano/sdk secrets fill` is for:
|
|
224
224
|
|
|
225
225
|
```bash
|
|
226
|
-
|
|
227
|
-
|
|
226
|
+
npx @xano/sdk secrets fill # every declared gate with no value gets one
|
|
227
|
+
npx @xano/sdk secrets fill ./xano/index.ts # name the entry when you are not in the project root
|
|
228
228
|
```
|
|
229
229
|
|
|
230
230
|
It mints a cryptographically random token per gate, the same shape a platform-minted one has,
|
|
@@ -260,7 +260,7 @@ cleared one.
|
|
|
260
260
|
One thing to clear out by hand if you used an earlier build: a `XANO_DOCS_TOKEN…` line left in
|
|
261
261
|
`xano/.env` from when tokens lived there is now an ordinary **backend** variable, because that file
|
|
262
262
|
is backend-only again. It will be sent as part of the workspace's env, where `env("NAME")` reads it
|
|
263
|
-
from every request. Delete the line — the value belongs in `xano/.secrets.json`, and `
|
|
263
|
+
from every request. Delete the line — the value belongs in `xano/.secrets.json`, and `npx @xano/sdk pull`
|
|
264
264
|
puts it there.
|
|
265
265
|
|
|
266
266
|
An entry the file holds that no scope in your source claims is **reported and never deleted** —
|
|
@@ -287,9 +287,9 @@ a rename, or to adopt an existing workspace object into code.
|
|
|
287
287
|
**`xano.lock`** freezes the whole workspace's identities at once — every auto-derived guid,
|
|
288
288
|
plus the `canonical` URL tokens of API groups and toolsets (which the engine otherwise
|
|
289
289
|
randomizes, giving the same code different public URLs per environment). Every command that
|
|
290
|
-
compiles an entry file writes it — `export`, `deploy`, `
|
|
290
|
+
compiles an entry file writes it — `export`, `deploy`, `preflight`, with no flag —
|
|
291
291
|
and updates it on every build, atomically, before the bundle. **Commit it next to your code.**
|
|
292
|
-
`npm run xano:check` is the CI guard (`
|
|
292
|
+
`npm run xano:check` is the CI guard (the `routes --strict` freshness check, then the project typecheck, then `npx @xano/sdk export ./xano/index.ts --check --strict`, which implies
|
|
293
293
|
`--frozen-lock`, writes nothing, and needs neither `xano/.env` nor `xano/.secrets.json`): it fails rather than change the lock,
|
|
294
294
|
so an uncommitted identity change is caught in review instead of on a deploy. It also fails
|
|
295
295
|
while the lock carries an entry no exported object matches. That entry is how a rename looks
|
|
@@ -316,7 +316,7 @@ delete-and-recreate of every object, reported as success. If the lock itself is
|
|
|
316
316
|
**Releasing to a workspace that already exists?** Adopt what it already serves *first*:
|
|
317
317
|
|
|
318
318
|
```bash
|
|
319
|
-
|
|
319
|
+
npx @xano/sdk lock import <its-packageExport.json> --lock=xano/xano.lock
|
|
320
320
|
```
|
|
321
321
|
|
|
322
322
|
Without that step your first locked build mints its own URL token for every API group that
|
|
@@ -333,7 +333,7 @@ explicitly with `--lock=<path>`.
|
|
|
333
333
|
Precedence at emit is always **explicit in-code value → lock entry → name derivation**.
|
|
334
334
|
|
|
335
335
|
**When the lock is actually load-bearing.** Because the default derivation is deterministic
|
|
336
|
-
— `md5("<
|
|
336
|
+
— `md5("<payloadKey>:<name>")` (the bundle's payload key: `dbo` for a table, `toolset` for an agent or MCP server), and `md5("query:<group>|<verb>|<name>")` for a query — a project
|
|
337
337
|
that created all of its own objects can regenerate a
|
|
338
338
|
byte-identical lock from its own source. Delete that lock, release again, and the same guids
|
|
339
339
|
come back: the objects match and update in place. For that project the lock is a *cache*, and
|
|
@@ -358,9 +358,9 @@ export warns about the orphaned entry and names the fix-up:
|
|
|
358
358
|
|
|
359
359
|
```bash
|
|
360
360
|
# code: defineFunction({ name: "signup" }) → { name: "register" }
|
|
361
|
-
|
|
362
|
-
|
|
363
|
-
|
|
361
|
+
npx @xano/sdk export ./xano/index.ts # stderr: lock entry "function:signup" matches no exported object…
|
|
362
|
+
npx @xano/sdk lock rename --entry=xano/index.ts function signup register
|
|
363
|
+
npx @xano/sdk export ./xano/index.ts # emits signup's original guid under "register" → engine renames in place
|
|
364
364
|
```
|
|
365
365
|
|
|
366
366
|
**Merge conflicts** — two branches that both touched the lock can conflict in git, and a
|
|
@@ -371,11 +371,11 @@ delete the markers. If both branches renamed the same object — one to `stock`,
|
|
|
371
371
|
Keep the name your code exports and drop the other; both commands read such a lock:
|
|
372
372
|
|
|
373
373
|
```bash
|
|
374
|
-
|
|
375
|
-
|
|
374
|
+
npx @xano/sdk lock rename --entry=xano/index.ts table stock goods # moves stock's identity onto goods
|
|
375
|
+
npx @xano/sdk lock prune --identity-only --yes table:stock --lock=xano/xano.lock # or just drop it
|
|
376
376
|
```
|
|
377
377
|
|
|
378
|
-
`rename`/`
|
|
378
|
+
`rename`/`import` take no entry file, so on their own they look for `xano.lock` in the
|
|
379
379
|
**current directory**. Pass `--entry=<path>` to derive it beside the entry the way
|
|
380
380
|
`export`/`deploy`/`prune` do, or `--lock=<path>` to name the file outright. They never
|
|
381
381
|
reach for a lock you did not point them at — when they spot one next door they say so and
|
|
@@ -383,17 +383,17 @@ stop, rather than writing a file you did not name.
|
|
|
383
383
|
|
|
384
384
|
**After `--replace`** — a replace rebuilds the workspace with fresh engine identities, so the
|
|
385
385
|
lock is stale the moment it finishes and the next ordinary merge would match nothing and
|
|
386
|
-
try to create everything. `
|
|
386
|
+
try to create everything. `npx @xano/sdk deploy ./xano/index.ts --to workspace --replace` now re-pins the lock from the rebuilt
|
|
387
387
|
workspace itself and tells you to commit it. If there is no lock to re-pin, it says so —
|
|
388
388
|
without one, the next merge duplicates every object.
|
|
389
389
|
|
|
390
|
-
**Importing a live workspace's identities** — `
|
|
390
|
+
**Importing a live workspace's identities** — `npx @xano/sdk lock import <bundle.json>` seeds the lock from a
|
|
391
391
|
real engine `packageExport`, capturing the live workspace's random guids by `(type, name)`
|
|
392
392
|
so code takes over an existing workspace and the first sync updates in place instead of
|
|
393
393
|
duplicating.
|
|
394
394
|
|
|
395
|
-
**CI** —
|
|
396
|
-
check an export runs and writes nothing, so it needs no secrets. It implies `--frozen-lock`, which
|
|
395
|
+
**CI** — the scaffolded `npm run xano:check` runs the `routes --strict` freshness check, the project typecheck, and
|
|
396
|
+
`npx @xano/sdk export ./xano/index.ts --check --strict`, which runs every check an export runs and writes nothing, so it needs no secrets. It implies `--frozen-lock`, which
|
|
397
397
|
fails instead of changing the lock, so a canonical
|
|
398
398
|
minted in a throwaway container can never silently diverge public URLs. Mint locally, commit
|
|
399
399
|
the lock. It fails on an entry no exported object matches too, which is the state a rename
|
package/guides/marketplace.md
CHANGED
|
@@ -7,14 +7,14 @@ An **add-on** is an ordinary npm package that declares itself to Xano SDK in its
|
|
|
7
7
|
marketplace` verbs that find one and change what your project has installed.
|
|
8
8
|
|
|
9
9
|
```bash
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
10
|
+
npx @xano/sdk marketplace list # every published add-on, newest first
|
|
11
|
+
npx @xano/sdk marketplace search auth # narrow by keyword
|
|
12
|
+
npx @xano/sdk marketplace details @xano-sdk/auth # what it installs, and how to register it
|
|
13
|
+
npx @xano/sdk marketplace details @xano-sdk/auth --prompt # ...as instructions for a coding agent
|
|
14
|
+
|
|
15
|
+
npx @xano/sdk marketplace install @xano-sdk/auth # add it to the project you are in
|
|
16
|
+
npx @xano/sdk marketplace reinstall <toolchain-package> # re-ask a toolchain module its questions
|
|
17
|
+
npx @xano/sdk marketplace remove <toolchain-package> # uninstall it and drop what it contributed
|
|
18
18
|
```
|
|
19
19
|
|
|
20
20
|
The split is deliberate. The three read verbs hit a public catalogue: no token, no
|
|
@@ -48,7 +48,11 @@ is compiled or a workspace is checked.
|
|
|
48
48
|
|
|
49
49
|
```
|
|
50
50
|
✓ Installed @xano-sdk/auth.
|
|
51
|
-
|
|
51
|
+
Not registered yet.
|
|
52
|
+
Add to xano/index.ts:
|
|
53
|
+
import { registerAuth } from "@xano-sdk/auth";
|
|
54
|
+
registerAuth(app, { canonical: "authn" });
|
|
55
|
+
Then run `npx @xano/sdk export ./xano/index.ts --out /dev/null && npm run xano:routes` to bring xano.lock and the route manifest up to date.
|
|
52
56
|
```
|
|
53
57
|
|
|
54
58
|
```
|
|
@@ -71,7 +75,7 @@ Both print a formatted summary to a terminal and stable JSON to a pipe. There is
|
|
|
71
75
|
discover: an agent gets the machine shape by doing what an agent already does.
|
|
72
76
|
|
|
73
77
|
```bash
|
|
74
|
-
|
|
78
|
+
npx @xano/sdk marketplace search auth | jq -r '.modules[].npm_package'
|
|
75
79
|
```
|
|
76
80
|
|
|
77
81
|
Each JSON row is the whole record `details` returns — `description`, `includes`,
|
|
@@ -111,12 +115,12 @@ The rendering has a fixed shape, filled from the module's own catalogue record:
|
|
|
111
115
|
Register it
|
|
112
116
|
<the xano/index.ts snippet, verbatim>
|
|
113
117
|
|
|
114
|
-
|
|
115
|
-
|
|
118
|
+
npx @xano/sdk marketplace install @scope/name
|
|
119
|
+
npx @xano/sdk marketplace details @scope/name --prompt to hand the wiring to a coding agent
|
|
116
120
|
```
|
|
117
121
|
|
|
118
122
|
The `Installs` rows carry one of `table`, `endpoint`, `function`, `task`, `trigger`, `agent`,
|
|
119
|
-
`mcp`, `middleware`. A toolchain module lists none of them, because it puts nothing on the
|
|
123
|
+
`tool`, `mcp`, `middleware`. A toolchain module lists none of them, because it puts nothing on the
|
|
120
124
|
workspace.
|
|
121
125
|
|
|
122
126
|
`--prompt` emits the publisher's own wiring instructions, raw and alone, written to be piped
|
|
@@ -142,22 +146,22 @@ tenant (`https://<instance>/tenant/<name>`) can stand in for it. See
|
|
|
142
146
|
## Installing
|
|
143
147
|
|
|
144
148
|
```bash
|
|
145
|
-
|
|
149
|
+
npx @xano/sdk marketplace install @xano-sdk/auth
|
|
146
150
|
```
|
|
147
151
|
|
|
148
152
|
The argument is resolved through the marketplace the way `details` resolves it, before npm
|
|
149
|
-
runs: a module's npm name or its slug (`
|
|
153
|
+
runs: a module's npm name or its slug (`npx @xano/sdk marketplace install auth` installs
|
|
150
154
|
`@xano-sdk/auth`), keeping any version or tag (`auth@next`). The install is then
|
|
151
155
|
`npm install` of that module's package. A name the marketplace does not list is refused
|
|
152
156
|
before npm runs, whatever its scope, with the not-found **exit 8** `details` uses
|
|
153
|
-
(`
|
|
157
|
+
(`npx @xano/sdk marketplace search <name>` finds the real one) — `install` adds marketplace modules,
|
|
154
158
|
not arbitrary npm packages. When the catalogue cannot be
|
|
155
159
|
reached, an `@xano-sdk/` name still installs as typed and any other name is refused. `file:`
|
|
156
160
|
paths, tarball URLs and git specs are installed as given, without a lookup.
|
|
157
161
|
|
|
158
162
|
What the command adds over typing `npm install` yourself is three things npm will not do:
|
|
159
163
|
|
|
160
|
-
1. **Add-ons are on the CLI's map.** `
|
|
164
|
+
1. **Add-ons are on the CLI's map.** `npx @xano/sdk --help` says they exist.
|
|
161
165
|
2. **It refuses before npm runs when you are not in a project.** This is the oldest reason
|
|
162
166
|
the command exists: run `npm install` from a parent directory and npm cheerfully creates
|
|
163
167
|
or mutates the wrong `package.json` and tells you it succeeded.
|
|
@@ -191,10 +195,10 @@ what happened to the file:
|
|
|
191
195
|
scaffolded with its add-ons already installed and registered:
|
|
192
196
|
|
|
193
197
|
```bash
|
|
194
|
-
|
|
198
|
+
npx @xano/sdk init my-app --marketplace @xano-sdk/auth,@xano-sdk/vector
|
|
195
199
|
```
|
|
196
200
|
|
|
197
|
-
`reinstall` and `remove` take those names too: `
|
|
201
|
+
`reinstall` and `remove` take those names too: `npx @xano/sdk marketplace remove auth` removes the
|
|
198
202
|
`@xano-sdk/auth` that `install auth` added. A name the project already depends on is taken as
|
|
199
203
|
typed, with no catalogue lookup, so both keep working offline. A name that is neither in the
|
|
200
204
|
project nor in the catalogue exits 8, as `install` does. `remove` is idempotent: removing a
|
|
@@ -253,12 +257,12 @@ only memory a module has.
|
|
|
253
257
|
no settings: the next `deploy` fires its hooks with an empty config and it runs on its own
|
|
254
258
|
fallbacks with nothing you chose. `export` and `deploy` report that state on every run,
|
|
255
259
|
because the likeliest way a module reaches it is a plain `npm install` or a merged PR,
|
|
256
|
-
neither of which runs
|
|
260
|
+
neither of which runs an SDK command:
|
|
257
261
|
|
|
258
262
|
```
|
|
259
263
|
! A toolchain module is installed but never configured, so it runs on its own
|
|
260
264
|
defaults with nothing this project chose.
|
|
261
|
-
@xano-sdk/xanoscript — configure it with `
|
|
265
|
+
@xano-sdk/xanoscript — configure it with `npx @xano/sdk marketplace install @xano-sdk/xanoscript`
|
|
262
266
|
```
|
|
263
267
|
|
|
264
268
|
Running `install` on a package that is already installed reads as a no-op until you know it
|
|
@@ -273,6 +277,7 @@ A module also contributes lines to your `.gitattributes`, in its own marked bloc
|
|
|
273
277
|
```
|
|
274
278
|
# xanosdk:begin @xano-sdk/xanoscript
|
|
275
279
|
# xanosdk 1.2.0 — generated; edits inside this block are overwritten
|
|
280
|
+
|
|
276
281
|
xanoscript/** linguist-generated
|
|
277
282
|
# xanosdk:end @xano-sdk/xanoscript
|
|
278
283
|
```
|
|
@@ -288,7 +293,7 @@ Each question a module declares derives a long flag that answers it, so a non-in
|
|
|
288
293
|
does not have to accept defaults:
|
|
289
294
|
|
|
290
295
|
```bash
|
|
291
|
-
|
|
296
|
+
npx @xano/sdk marketplace install @xano-sdk/xanoscript --xanoscript --xanoscript-dir=generated
|
|
292
297
|
```
|
|
293
298
|
|
|
294
299
|
A `string` or `choice` question takes `--flag=value`, not `--flag value`. The CLI cannot know
|
|
@@ -314,7 +319,7 @@ setting on the next run.
|
|
|
314
319
|
## Re-asking: reinstall
|
|
315
320
|
|
|
316
321
|
```bash
|
|
317
|
-
|
|
322
|
+
npx @xano/sdk marketplace reinstall @xano-sdk/xanoscript
|
|
318
323
|
```
|
|
319
324
|
|
|
320
325
|
`reinstall` re-runs npm, then re-asks one module its questions and reconciles, offering your
|
|
@@ -347,7 +352,7 @@ every prompt and finding your chosen directory reverted.
|
|
|
347
352
|
## Removing
|
|
348
353
|
|
|
349
354
|
```bash
|
|
350
|
-
|
|
355
|
+
npx @xano/sdk marketplace remove @xano-sdk/xanoscript
|
|
351
356
|
```
|
|
352
357
|
|
|
353
358
|
`remove` uninstalls the package and then drops the settings and the contributed lines
|
|
@@ -362,10 +367,11 @@ run. A `--frozen-lock` run in that state exits 0 having verified less than it di
|
|
|
362
367
|
and says nothing. Only the next `install`, `reinstall` or `remove` drops the stale block.
|
|
363
368
|
|
|
364
369
|
The state that does fail **every** `--frozen-lock` run is the other one: a module still
|
|
365
|
-
declared in `dependencies`
|
|
366
|
-
--no-save`, a deleted `node_modules/<pkg>` or a
|
|
367
|
-
project still says the module is expected, so its
|
|
368
|
-
away
|
|
370
|
+
declared in `dependencies` and configured in the `"xanosdk"` block but missing from
|
|
371
|
+
`node_modules`, which is what `npm uninstall --no-save`, a deleted `node_modules/<pkg>` or a
|
|
372
|
+
drifted lockfile leaves behind. There the project still says the module is expected, so its
|
|
373
|
+
absence is reported rather than assumed away (an unconfigured dependency that is missing is
|
|
374
|
+
an ordinary package as far as the loader can tell, and is not reported):
|
|
369
375
|
|
|
370
376
|
```
|
|
371
377
|
A toolchain module could not be loaded, so whatever it checks was not checked — and
|
|
@@ -426,7 +432,7 @@ than a warning, and so is a hook that throws.
|
|
|
426
432
|
On a normal run both are reported and skipped, matching every other optional side effect in
|
|
427
433
|
the CLI. The asymmetry exists because if a plugin fails to resolve in CI (a partial install, a
|
|
428
434
|
stale plugin path after a version bump) then its hook never fires, nothing checks what it
|
|
429
|
-
checks, and `
|
|
435
|
+
checks, and `npx @xano/sdk export ./xano/index.ts --frozen-lock` exits 0 against a tree that is wrong. A red guard
|
|
430
436
|
gets fixed; a green one gets trusted.
|
|
431
437
|
|
|
432
438
|
A module's own check therefore rides on the same `--frozen-lock` run as `xano.lock`, so a
|
|
@@ -27,7 +27,7 @@ and defaulting the other way would strand them. A `kind` the SDK does not recogn
|
|
|
27
27
|
defaulted to one kind or the other: the failure a default would produce is a module reported
|
|
28
28
|
as unwired when its only fault is a typo in one string.
|
|
29
29
|
|
|
30
|
-
What that costs you depends on where the typo is read. `
|
|
30
|
+
What that costs you depends on where the typo is read. `npx @xano/sdk init` refuses by name, with
|
|
31
31
|
the valid kinds listed, because a scaffold that silently drops your module is worse than one
|
|
32
32
|
that stops. Every other path, the marketplace verbs and the CLI's own module loading
|
|
33
33
|
included, warns and reads the package as an ordinary dependency rather than taking a whole
|
|
@@ -76,7 +76,7 @@ register function being read. Declare `"options": {}` and the call is written ba
|
|
|
76
76
|
**Omit the key and your module has said nothing either way**, so the SDK imports your entry
|
|
77
77
|
and measures `register`'s arity. A function that takes a second parameter nobody declared is
|
|
78
78
|
left **out** of the generated `xano/index.ts` rather than called without it, with a commented
|
|
79
|
-
call and a pointer to `
|
|
79
|
+
call and a pointer to `npx @xano/sdk marketplace details <pkg> --prompt`. The call would not compile,
|
|
80
80
|
and a fresh scaffold that passes `npm run typecheck` is worth more than one that has your
|
|
81
81
|
module in it.
|
|
82
82
|
|
|
@@ -128,9 +128,12 @@ your module is only correct against the SDK versions whose shapes it understands
|
|
|
128
128
|
range out with a floor and a ceiling, as above: the ceiling is the next major, so a module
|
|
129
129
|
built for 1.x loads on every 1.x SDK and is refused on 2.0.
|
|
130
130
|
|
|
131
|
-
That range is **enforced at load
|
|
131
|
+
That range is **enforced at load**. On `export`, `deploy`, `preflight` and `init`, an SDK outside it
|
|
132
132
|
is refused by name before your plugin file is imported, naming the range you asked for and the
|
|
133
|
-
version it got.
|
|
133
|
+
version it got. The `routes.gen.ts` writers (`routes --emit`, the marketplace's route refresh,
|
|
134
|
+
`pull`, `generate`) and the marketplace reconcile skip the module with a warning instead: it is
|
|
135
|
+
never imported, a routes writer keeps its previous block, and `routes --emit --strict` still
|
|
136
|
+
fails. So the floor is the version whose shapes your hooks understand, not an
|
|
134
137
|
aspiration — declare it accurately and the SDK will never quietly run your module against a
|
|
135
138
|
contract it was not built for. Ranges are read as `>=` / `>` / `<=` / `<` / `=` comparators,
|
|
136
139
|
`^`, `~`, exact pins and `||` unions of those; a shape outside that subset is not refused, it
|
|
@@ -218,7 +221,7 @@ questions: [
|
|
|
218
221
|
Two reasons the callback form does not exist, and both are hard. A callback would let a
|
|
219
222
|
module hang a command on a TTY read in CI, where there is no one to answer it, and the SDK
|
|
220
223
|
could not even impose a timeout because it cannot tell a slow prompt from a slow computation.
|
|
221
|
-
And `
|
|
224
|
+
And `npx @xano/sdk init --web` renders the questionnaire as a browser form, which can display a list
|
|
222
225
|
of choices but cannot run your callback at all. Declaring the question as data means the SDK
|
|
223
226
|
owns every way of answering it.
|
|
224
227
|
|
|
@@ -281,7 +284,7 @@ which command is running and no access to the filesystem, and it may be called s
|
|
|
281
284
|
in one run and must return the same thing for the same answers.
|
|
282
285
|
|
|
283
286
|
That is what makes the reconcile idempotent. A module is configured whenever its project is
|
|
284
|
-
reconciled, and `
|
|
287
|
+
reconciled, and `npx @xano/sdk init` is only the first of those moments: installing into a project
|
|
285
288
|
that already exists, re-answering later, and removing all run the same pass. The correct
|
|
286
289
|
state is a function of the project's dependencies and its stored answers, so it can be
|
|
287
290
|
rebuilt from scratch at any moment, however your module arrived.
|
|
@@ -394,7 +397,7 @@ read than it is slow.
|
|
|
394
397
|
| `BundleContext` | What it carries |
|
|
395
398
|
|---|---|
|
|
396
399
|
| `bundle.payload` | The compiled payload, keyed by payload key (`table`, `query`, `app`, ...). |
|
|
397
|
-
| `entry` | The entry file the bundle came from. **Absent** on the `--bundle <path>` branch. |
|
|
400
|
+
| `entry` | The entry file the bundle came from. **Absent** on the `--bundle <path>` branch, and when `deploy` fetches a remote source (`release:main`). |
|
|
398
401
|
| `cwd` | The project root every relative path resolves against. |
|
|
399
402
|
| `command` | `"export"` or `"deploy"`. |
|
|
400
403
|
| `frozen` | The run is `--frozen-lock` (or `export --check` / `deploy --to … --dry-run`, which imply it): a verification, not a write. |
|
|
@@ -403,7 +406,7 @@ read than it is slow.
|
|
|
403
406
|
|
|
404
407
|
**`entry` is optional rather than a made-up path** so a plugin may decline the
|
|
405
408
|
`--bundle <path>` branch, where the input is already-serialized text with no entry and no
|
|
406
|
-
registry behind it. A tree rendered from a bundle the project did not compile describes
|
|
409
|
+
registry behind it, and a `deploy` from a fetched source, where nothing local was compiled. A tree rendered from a bundle the project did not compile describes
|
|
407
410
|
something other than the source beside it.
|
|
408
411
|
|
|
409
412
|
**Under `frozen` a plugin must compare and report, never write.** It is also the mode in which
|
|
@@ -428,7 +431,7 @@ onPreflight: async (ctx) => {
|
|
|
428
431
|
},
|
|
429
432
|
```
|
|
430
433
|
|
|
431
|
-
Fires on `
|
|
434
|
+
Fires on `npx @xano/sdk preflight`, contributing a comparison to the report.
|
|
432
435
|
|
|
433
436
|
| `PreflightContext` | What it carries |
|
|
434
437
|
|---|---|
|
|
@@ -469,9 +472,11 @@ const plugin: ToolchainPlugin = {
|
|
|
469
472
|
```
|
|
470
473
|
|
|
471
474
|
Your module's section of the route manifest, `xano/routes.gen.ts`. It runs wherever that file
|
|
472
|
-
is written: `
|
|
473
|
-
`xano:routes`), `
|
|
474
|
-
`remove` make, so your
|
|
475
|
+
is written: `npx @xano/sdk routes ./xano/index.ts --emit xano/routes.gen.ts` (the scaffold's
|
|
476
|
+
`xano:routes`), `init --marketplace` when it writes the project's first manifest, `pull`,
|
|
477
|
+
`generate`, and the refresh `marketplace install`, `reinstall` and `remove` make, so your
|
|
478
|
+
block lands with your module. Not `init --from`: a project it creates has no module installed
|
|
479
|
+
yet, and the first `xano:routes` after an install adds your section.
|
|
475
480
|
|
|
476
481
|
| `RoutesManifestContext` | What it carries |
|
|
477
482
|
|---|---|
|
|
@@ -512,7 +517,7 @@ the file free of the SDK runtime in a frontend bundle. Declare yours in `imports
|
|
|
512
517
|
subpaths, a relative or absolute path, and a protocol (`node:`) are all refused, naming your
|
|
513
518
|
module. Each name must be a plain identifier, with no `as` rename. A package you import must
|
|
514
519
|
resolve from the user's project, so declare it in your `peerDependencies`:
|
|
515
|
-
`
|
|
520
|
+
`npx @xano/sdk marketplace install` adds each peer other than `@xano/sdk` that the project does not
|
|
516
521
|
already declare as a direct dependency, with your range, through the project's package manager.
|
|
517
522
|
|
|
518
523
|
**Synchronous and pure.** No filesystem, network, clock or randomness: the same context must
|
|
@@ -564,7 +569,7 @@ and refuses it by name, with the upgrade to make.
|
|
|
564
569
|
| Shape | Why it is refused | The fix |
|
|
565
570
|
|---|---|---|
|
|
566
571
|
| A `files` hook and no `contributes` | `files` was renamed once the hook stopped running only at scaffold time. | Rename it. `contributes(answers)` returns a `ProjectContributions`. |
|
|
567
|
-
| A `ciSteps` entry in what `contributes` returns | The slot is gone. Your check already rides on `
|
|
572
|
+
| A `ciSteps` entry in what `contributes` returns | The slot is gone. Your check already rides on `npx @xano/sdk export ./xano/index.ts --frozen-lock` through `onBundle` with `frozen` set. | Drop it. No workflow step of your own is needed. |
|
|
568
573
|
| `contributes` returning a string, a number, an array or a Promise | Indistinguishable from "contributed nothing", which is recorded as switched off. | Return an object, or nothing at all. `contributes` is synchronous. |
|
|
569
574
|
| A default export whose `kind` is not `"toolchain"` | The manifest and the module disagree, so one of the two is stale. | Make them agree. |
|
|
570
575
|
| An SDK outside your declared `peerDependencies["@xano/sdk"]` range | Your hooks were written against shapes this SDK does not have, so it would apply nothing. | Upgrade the SDK, or install a build of your module made for it. |
|
|
@@ -623,7 +628,7 @@ Things worth proving about your own module:
|
|
|
623
628
|
|
|
624
629
|
## Publishing
|
|
625
630
|
|
|
626
|
-
Publish to npm like any package. To appear in `
|
|
631
|
+
Publish to npm like any package. To appear in `npx @xano/sdk marketplace list` and `search`, the
|
|
627
632
|
module also needs a catalogue entry, which carries its title, tagline, description, tags, the
|
|
628
633
|
objects it installs, what the user supplies, the registration snippet, and the agent prompt
|
|
629
634
|
`details --prompt` emits. Write that prompt for a machine: it is what `init --marketplace`
|
package/guides/object-kinds.md
CHANGED
|
@@ -14,11 +14,14 @@ and the seven trigger factories below. Signatures and payload keys are in
|
|
|
14
14
|
the types don't tell you.
|
|
15
15
|
|
|
16
16
|
**A knowledge item's body is a file, and `mode` is a running cost.** `knowledge()` is the
|
|
17
|
-
markdown
|
|
17
|
+
markdown shared by every AI that builds this backend — Xano's AI builder, people authoring in
|
|
18
|
+
XanoScript, and your local coding agent, which reads the same `.md` files in the repo (deploy
|
|
19
|
+
and `pull` keep them in sync). An `agent()` run never reads it; put what that agent needs in
|
|
20
|
+
its `llm.systemPrompt`. It is the one kind whose payload
|
|
18
21
|
is prose — so the body is named by path (`knowledgeFile("./runbook.md", import.meta.url)`)
|
|
19
|
-
rather than written as a string, and `refs: knowledgeDir(...)` ships a whole folder
|
|
20
|
-
|
|
21
|
-
symlink is not followed. What the
|
|
22
|
+
rather than written as a string, and `refs: knowledgeDir(...)` ships a whole folder Xano's AI
|
|
23
|
+
builder searches on demand — UTF-8 text files only (other content is refused), and a
|
|
24
|
+
symlink is not followed. What the builder actually receives is decided by `type` and `mode`,
|
|
22
25
|
and nothing in the types warns you: an `agents.md` item is injected in full on every turn
|
|
23
26
|
whatever `mode` says, `mode: "always"` spends the body's whole length on every request, and
|
|
24
27
|
the default `mode: "auto"` sends only the name and `description` until a request matches.
|
|
@@ -130,7 +133,7 @@ query({
|
|
|
130
133
|
|
|
131
134
|
A pull brings tests back, along with a query's saved request/response `example`. The one
|
|
132
135
|
thing it withholds is a test's auth `token` — that is an expiring credential rather than
|
|
133
|
-
authored configuration, so `
|
|
136
|
+
authored configuration, so `npx @xano/sdk init --from` reports it as a deliberate omission instead of
|
|
134
137
|
writing it into a committed tree.
|
|
135
138
|
|
|
136
139
|
**Four of the `Run …` statements only run inside a workflow test.** `s.api.call`,
|
|
@@ -139,7 +142,7 @@ run time, and outside a `workflowTest` stack it cannot reach the target — so o
|
|
|
139
142
|
a query, function or task type-checks, exports, imports and **deploys clean**, then answers
|
|
140
143
|
the first real request
|
|
141
144
|
with `ERROR_FATAL: <Type> does not exist`. It is not per host kind: the same call fails
|
|
142
|
-
identically from a function that a query runs. `
|
|
145
|
+
identically from a function that a query runs. `npx @xano/sdk export` refuses them outside a
|
|
143
146
|
workflow test. `s.function.call`, `s.tool.call`, `s.middleware.call` and `s.addon.call` run
|
|
144
147
|
from any stack, as does `s.function.run` — the ordinary way to invoke a function. To share
|
|
145
148
|
logic between two endpoints, put it in a `defineFunction` and `s.function.run` it from both.
|
|
@@ -173,7 +176,7 @@ realtimeMessage({
|
|
|
173
176
|
name: "send", // `input` types the message PAYLOAD
|
|
174
177
|
channel: room, // the handle carries the server too
|
|
175
178
|
input: { body: input.text({ required: true }) },
|
|
176
|
-
deliverTo: "channel", // or "sender" (request/response) / "others"
|
|
179
|
+
deliverTo: "channel", // or "sender" (request/response) / "others" / "explicit"
|
|
177
180
|
stack: [s.debug.log({ value: inp("body") })],
|
|
178
181
|
});
|
|
179
182
|
```
|
|
@@ -348,10 +351,10 @@ a microservice fixes every call site at once. A plain `"name:port"` string is al
|
|
|
348
351
|
and is the only way to reach an instance-level microservice, which isn't a workspace object;
|
|
349
352
|
nothing checks that spelling, so prefer the def wherever there is one.
|
|
350
353
|
|
|
351
|
-
A container takes time to come up, so `
|
|
354
|
+
A container takes time to come up, so `npx @xano/sdk deploy` waits for it: after the import it
|
|
352
355
|
reads each microservice and reports whether it is ready, still starting, or failed, then
|
|
353
356
|
lists them. Skip the wait with `--skip-liveness`. The same report is available any time from
|
|
354
|
-
`
|
|
357
|
+
`npx @xano/sdk status`, `npx @xano/sdk ephemeral get <name>`, and `npx @xano/sdk workspace details`.
|
|
355
358
|
|
|
356
359
|
Two outcomes, and only one of them is a warning:
|
|
357
360
|
|
|
@@ -31,7 +31,7 @@ Paths are lower case throughout — an HTTP verb is the one exception, because i
|
|
|
31
31
|
the method rather than a word. Bindings keep the object's own casing, so a file name
|
|
32
32
|
and the symbol it exports can differ.
|
|
33
33
|
|
|
34
|
-
That is the shape `
|
|
34
|
+
That is the shape `npx @xano/sdk init --from` writes, and its `index.ts` re-exports every object
|
|
35
35
|
by name — import from the tree's root rather than from a file, since a file path moves
|
|
36
36
|
when an object's parent or its `_shared.ts` placement changes. Hand-authored projects are
|
|
37
37
|
free to use any other layout; only `index.ts` registering the objects matters.
|
|
@@ -40,15 +40,15 @@ free to use any other layout; only `index.ts` registering the objects matters.
|
|
|
40
40
|
`new Xano().registerWorkspace({ name: "my-app" })`, returning the same chainable registry.
|
|
41
41
|
Authoring is **declarative def-objects** passed to factories; there is no callback/chaining
|
|
42
42
|
builder. `xano.export()` returns the importable `packageExport` bundle, and
|
|
43
|
-
`
|
|
43
|
+
`npx @xano/sdk export`/`deploy` read the module's default export.
|
|
44
44
|
|
|
45
45
|
## Wiring a project by hand
|
|
46
46
|
|
|
47
|
-
`
|
|
47
|
+
`npx @xano/sdk init` writes all of this for you. Without it, two lines set a project up:
|
|
48
48
|
|
|
49
49
|
```bash
|
|
50
50
|
npm init -y && npm pkg set type=module && npm install -D @xano/sdk
|
|
51
|
-
npx
|
|
51
|
+
npx @xano/sdk upgrade # rewrites npm's caret to the range init writes
|
|
52
52
|
```
|
|
53
53
|
|
|
54
54
|
Write your workspace in `xano/index.ts`; `login` and `deploy` are unchanged. `type=module`
|