@widgetic/creator 0.3.49

package/README.md

@@ -0,0 +1,116 @@
+# Widget Creator – Local Development Notes
+
+## VM Preview Configuration
+
+The Widget Preview modal proxies through the API Gateway. Configure the front-end by creating or updating `.env.local` with:
+
+```
+VITE_WIDGET_VM_PREVIEW_ORIGIN=http://localhost:3000/v1/agent
+```
+
+After editing the file, restart `pnpm dev` so Vite reloads the environment variables. When a VM session is selected, the modal and “Open in new tab” button will hit:
+
+```
+{VITE_WIDGET_VM_PREVIEW_ORIGIN}/vms/{vmSessionId}/preview
+```
+
+If the variable is missing, the UI shows guidance and logs a single warning in development.
+
+---
+
+# create-svelte
+
+Everything you need to build a Svelte project, powered by [`create-svelte`](https://github.com/sveltejs/kit/tree/main/packages/create-svelte).
+
+## Creating a project
+
+If you're seeing this, you've probably already done this step. Congrats!
+
+```bash
+# create a new project in the current directory
+npm create svelte@latest
+
+# create a new project in my-app
+npm create svelte@latest my-app
+```
+
+## Developing
+
+Once you've created a project and installed dependencies with `npm install` (or `pnpm install` or `yarn`), start a development server:
+
+```bash
+npm run dev
+
+# or start the server and open the app in a new browser tab
+npm run dev -- --open
+```
+
+## Building
+
+To create a production version of your app:
+
+```bash
+npm run build
+```
+
+You can preview the production build with `npm run preview`.
+
+> To deploy your app, you may need to install an [adapter](https://kit.svelte.dev/docs/adapters) for your target environment.
+
+
+
+
+
+o make it work with both Svelte 4 and Svelte 5, we need to take a more flexible approach. Here's how you can resolve this:
+
+1. First, remove the specific Svelte dependency from your project:
+```bash
+npm uninstall svelte
+``` 
+
+2. Install svelte-preprocess-react as a dev dependency:
+```bash
+npm install --save-dev svelte-preprocess-react
+```
+
+3. In your package.json, add a peer dependency for Svelte that allows both version 4 and 5:
+```json
+"svelte": "^4.0.0 || ^5.0.0-next.0"
+```
+
+4. Update your svelte.config.js (or create one if it doesn't exist) to use svelte-preprocess-react:
+```js
+import preprocessReact from 'svelte-preprocess-react/preprocessReact';
+
+export default {
+	preprocess: [preprocessReact()]
+};
+``` 
+
+5. In your project's root, create a .npmrc file (if it doesn't exist) and add:
+```bash
+legacy-peer-deps=true
+```
+This allows npm to install packages with peer dependencies that don't strictly match.
+
+6. Clear your npm cache:
+```bash
+npm cache clean --force
+```
+
+7. Remove the node_modules folder and package-lock.json:
+```bash
+rm -rf node_modules package-lock.json
+```
+
+8. Reinstall dependencies:
+```bash
+npm install
+```
+
+These steps should resolve the dependency conflicts and allow your project to work with both Svelte 4 and Svelte 5. The key points are:
+- Using peer dependencies to allow flexibility in the Svelte version.
+- Using svelte-preprocess-react as a dev dependency to handle React preprocessing.
+- Allowing legacy peer dependencies to resolve version conflicts.
+- Remember to adjust your code to be compatible with both Svelte 4 and Svelte 5 syntax where necessary. For example, use conditional imports or runtime checks to handle differences between versions.
+- If you still encounter issues, you might need to review other dependencies in your project that might be causing conflicts with Svelte versions.