Release v2

.gitignore

@@ -1,7 +1,13 @@
 node_modules
+.pnpm-store
 .DS_Store
 
 # dev folders
 stylesheets
 components
 .raisely.json
+.idea
+
+# allow test fixtures even when their folder names match the dev ignores above
+!tests/
+!tests/**

CHANGELOG.md

@@ -1,4 +1,11 @@
 
+# 2.0.0
+- Breaking layout change: per-campaign content now lives in `campaigns/<campaign-path>/`, the entry SCSS file is now `main.scss`, and shared components remain at the repo root.
+- Added `raisely migrate` to upgrade existing repositories from the v1 layout to the v2 layout.
+- Added SCSS and component validation for `raisely deploy` (with `--no-validate`) and per-save validation for `raisely start`.
+- Improved `raisely local` resilience by serving the last successful CSS when compilation fails, removing the 5-second retry loop, and removing process exit on transpiler 401 responses.
+- Removed v1 compatibility read paths; v2 commands now require the v2 layout.
+
 # 1.8.3
 - Fix redirects for `raisely local`
 

README.md

@@ -2,13 +2,13 @@
 
 ![Raisely logo](https://raisely-images.imgix.net/www/uploads/lockup-default-svg-d0b31f.svg?fit=max&w=300&auto=format&q=62)
 
-The Raisely CLI is used to power local development of Raisely themes, syncing custom components and campaign styles to your local machine.
+The Raisely CLI is used to power local development of Raisely themes, syncing custom components, campaign styles, and campaign pages to your local machine.
 
-For more about Raisely, see <https://raisely.com>
+For more about Raisely, see [https://raisely.com](https://raisely.com)
 
 ## Overview
 
-The Raisely CLI allows for fast and easy development on the Raisely platform. The CLI allows you to connect a directory on your local computer to a Raisely account. With the CLI you can update campaign stylesheets, and edit and create custom React components.
+The Raisely CLI allows for fast and easy development on the Raisely platform. The CLI allows you to connect a directory on your local computer to a Raisely account. With the CLI you can update campaign stylesheets, edit and create custom React components, and edit page layout JSON under `campaigns/<campaign-path>/pages/`.
 
 The CLI is built on Node.js, so you'll need Node.js installed to use it.
 
@@ -25,27 +25,90 @@ For other issues, [submit a support ticket](mailto:support@raisely.com).
 1. Install the CLI globally: `npm install @raisely/cli -g`
 2. Go into your working directory and run: `raisely init`
 
+`raisely init` writes the v2 project layout:
+
+```text
+campaigns/
+  <campaign-path>/
+    pages/
+      home.json
+    stylesheets/
+      main.scss
+components/
+  CustomHeader.js
+```
+
 ## Commands
 
-- `raisely init` - start a new Raisely project, authenticate and sync your campaigns
-- `raisely update` - update local copies of styles and components from the API
-- `raisely create [name]` - create a new custom component, optionally add the component name to the command (otherwise you will be asked for one)
-- `raisely start` - starts watching for and uploading changes to styles and components
-- `raisely deploy` - deploy your local code to Raisely
-- `raisely local` - work locally on a Raisely campaign without syncing changes up
+-   `raisely init` - start a new Raisely project and sync your campaigns
+-   `raisely init --uuid <uuid>` - initialize directly against a specific campaign, skipping the picker
+-   `raisely list` - list every campaign (Name, Uuid), sorted A-Z; prints a padded table in a terminal, TSV when stdout is piped (`raisely list | cut -f2`), and `--json` / `--tsv` force a format
+-   `raisely login` - sign in with OAuth (opens your browser); stores access and refresh tokens in the OS keychain
+-   `raisely logout` - revoke the current access token when possible and clear keychain storage for this org
+-   `raisely update` - update local copies of styles, components, and pages from the API
+-   `raisely update --force` - same as above without the confirmation prompt (for CI/scripts)
+-   `raisely migrate` - migrate an existing repo from the legacy layout to the v2 layout
+-   `raisely create [name]` - create a new custom component, optionally add the component name to the command (otherwise you will be asked for one)
+-   `raisely start` - starts watching for and uploading validated changes to styles and components
+-   `raisely deploy` - deploy your local code to Raisely (styles, components, and pages)
+-   `raisely deploy --no-validate` - deploy without running pre-flight validation first
+-   `raisely local` - work locally on a Raisely campaign without syncing changes up (includes local page JSON overrides from `campaigns/<campaign-path>/pages/` when present)
+-   `raisely local --uuid <uuid>` - open a specific campaign by UUID, skipping the picker
+-   `raisely local --port <port>` - run the local development server on a custom port instead of `8015`
+-   `raisely media list` - list all media assets for a campaign or organisation; falls back to the first campaign in `.raisely.json` when no flag is passed
+-   `raisely media list --campaign <slug>` - list media for a specific campaign by path/slug
+-   `raisely media list --organisation <uuid>` - list media for an organisation by UUID
+-   `raisely media list --json` - output the media array as JSON instead of a table
+-   `raisely media delete <uuid>` - delete a media asset by UUID (no confirmation prompt)
+-   `raisely media upload <file-or-url>` - upload a local file or a public URL as a media asset; falls back to the first campaign in `.raisely.json` when no `--campaign` is passed
+-   `raisely media upload <file-or-url> --campaign <slug>` - upload to a specific campaign
+-   `raisely media upload <file-or-url> --organisation <uuid>` - upload to an organisation
+-   `raisely media upload <file-or-url> --force` - skip the confirmation prompt (required for non-interactive/agent use)
+-   `raisely media upload <file-or-url> --json` - skip the confirmation prompt and output the result as JSON
+
+### Custom public host (`raisely local`)
+
+By default, `raisely local` proxies to `https://{campaign.path}.raisely.com`. If the site people visit is on another host (for example `https://{campaign.path}.raiselysite.com`), add `**proxyUrl**` to `.raisely.json` with the bare domain (no campaign subdomain):
+
+```json
+{
+	"proxyUrl": "https://raiselysite.com"
+}
+```
+
+The CLI turns that into `https://{campaign.path}.raiselysite.com` so the proxy matches production.
+
+## Authentication
+
+Interactive use relies on **OAuth 2.0 with PKCE** against `https://api.raisely.com/v1/oauth/authorize` and `/v1/oauth/token` (or your `RAISELY_API_URL` host for staging, for example `https://api.raisely.io`).
+
+1. Register a **NATIVE** app in Raisely admin (Settings → Apps), add loopback redirect URIs such as `http://127.0.0.1:8765/callback` (and 8766, 8767), and note the app `client_id` (UUID).
+2. Set `**RAISELY_OAUTH_CLIENT_ID`\*\* to that UUID before running `raisely login` or `raisely init`. The CLI ships with a placeholder `client_id` until you replace it in the package.
+3. Optional: `**RAISELY_OAUTH_SCOPES**` overrides the default scopes (`campaigns:read campaigns:update pages:read`).
+
+Tokens are stored in the OS keychain under service `@raisely/cli`, with account name `{api_host}:{organisation_uuid}` (for example `api.raisely.com:aaaaaaaa-...`). The file `~/.raisely/session.json` records the last successful login’s host and organisation so commands work before `.raisely.json` exists.
+
+**Credential resolution order** for API calls:
+
+1. `RAISELY_TOKEN` (personal access token / campaign key), if set
+2. Keychain session for the current API host + `organisationUuid` (from `.raisely.json` or the session pointer)
+3. Legacy `token` field in `.raisely.json`
 
 ## CI/CD Usage
 
 Raisely CLI supports usage in a CI/CD environment for auto-deployment of styles and components. In this scenario you would use the CLI to deploy local code, and overwrite what is on a Raisely campaign or account.
 
 Raisely CLI supports the following environment variables:
 
-- `RAISELY_TOKEN` – your API secret key
-- `RAISELY_CAMPAIGNS` - a comma-separated list of campaign uuids to sync (so you can be selective)
+-   `RAISELY_TOKEN` – your API secret key (overrides keychain and `.raisely.json` token)
+-   `RAISELY_CAMPAIGNS` - a comma-separated list of campaign uuids to sync (so you can be selective)
+-   `RAISELY_OAUTH_CLIENT_ID` - OAuth NATIVE app client id (required for `raisely login` until a built-in id ships)
+-   `RAISELY_OAUTH_SCOPES` - optional space-separated OAuth scopes
+-   `RAISELY_API_URL` - API base URL (default `https://api.raisely.com`)
 
 _Note: All components are always synced, when they're present in the directory your syncing_
 
-With these environment variables set, run: `raisely deploy`. This will sync your local directory to the remote Raisely account, overwriting the styles and components on the destination campaign.
+With these environment variables set, run: `raisely deploy`. This will sync your local directory to the remote Raisely account, overwriting the styles, components, and pages on the destination campaign.
 
 ## Developing
 

package.json

@@ -1,45 +1,50 @@
 {
 	"name": "@raisely/cli",
-	"version": "1.8.3",
+	"version": "2.0.0",
 	"description": "Raisely CLI for local development",
 	"main": "./src/cli.js",
 	"type": "module",
 	"bin": {
 		"raisely": "./bin/raisely.js"
 	},
 	"scripts": {
-		"test": "echo \"Error: no test specified\" && exit 1"
+		"test": "vitest run --config vitest.config.js"
 	},
 	"engines": {
 		"node": ">=18"
 	},
 	"author": "Raisely",
 	"license": "SEE LICENSE IN LICENSE.md",
 	"dependencies": {
-		"@babel/core": "^7.17.8",
-		"@babel/plugin-proposal-class-properties": "^7.16.7",
-		"@babel/preset-env": "^7.16.11",
-		"@babel/preset-react": "^7.16.7",
-		"chalk": "^2.4.2",
-		"commander": "^9.2.0",
-		"express": "^4.17.3",
-		"folder-hash": "^4.0.2",
-		"fzstd": "^0.1.1",
-		"glob": "^7.1.6",
-		"glob-promise": "^3.4.0",
-		"http-proxy-middleware": "^2.0.4",
-		"inquirer": "^6.3.1",
-		"jwt-decode": "^3.0.0-beta.2",
-		"lodash": "^4.17.11",
-		"node-fetch": "^3.2.3",
-		"node-sass": "^9.0.0",
-		"node-watch": "^0.7.1",
-		"open": "^8.4.0",
-		"ora": "^3.4.0",
-		"p-limit": "^4.0.0"
+		"@babel/core": "7.12.10",
+		"@babel/helpers": "7.12.5",
+		"@babel/plugin-proposal-class-properties": "7.12.1",
+		"@babel/plugin-transform-regenerator": "7.12.1",
+		"@babel/preset-env": "7.12.11",
+		"@babel/preset-react": "7.12.10",
+		"@napi-rs/keyring": "1.3.0",
+		"chalk": "5.6.2",
+		"commander": "13.1.0",
+		"express": "5.2.1",
+		"folder-hash": "4.1.2",
+		"form-data": "4.0.6",
+		"fzstd": "0.1.1",
+		"glob": "8.1.0",
+		"glob-promise": "6.0.7",
+		"handlebars": "4.7.9",
+		"http-proxy-middleware": "3.0.5",
+		"inquirer": "12.11.1",
+		"jwt-decode": "4.0.0",
+		"lodash": "4.18.1",
+		"node-fetch": "3.3.2",
+		"node-watch": "0.7.4",
+		"open": "10.2.0",
+		"ora": "8.2.0",
+		"p-limit": "6.2.0"
 	},
 	"devDependencies": {
-		"prettier": "^2.6.2"
+		"prettier": "3.8.3",
+		"vitest": "2.1.9"
 	},
 	"repository": {
 		"type": "git",