create-outsystems-astro 0.4.2 → 0.5.0

package/README.md

@@ -93,6 +93,7 @@ All commands are run from the root of the project, from a terminal:
 | `npm run preview`         | Preview build locally, before creating output    |
 | `npm run astro ...`       | Run CLI commands like `astro add`, `astro check` |
 | `npm run astro -- --help` | Get help using the Astro CLI                     |
+| `npm run audit:npm`       | Run audit of modules                             |
 
 ### Yarn
 
@@ -105,6 +106,7 @@ All commands are run from the root of the project, from a terminal:
 | `yarn run preview`         | Preview build locally, before creating output    |
 | `yarn run astro ...`       | Run CLI commands like `astro add`, `astro check` |
 | `yarn run astro -- --help` | Get help using the Astro CLI                     |
+| `yarn run audit:yarn`      | Run audit of modules                             |
 
 ### pnpm
 
@@ -117,6 +119,7 @@ All commands are run from the root of the project, from a terminal:
 | `pnpm run preview`         | Preview build locally, before creating output    |
 | `pnpm run astro ...`       | Run CLI commands like `astro add`, `astro check` |
 | `pnpm run astro -- --help` | Get help using the Astro CLI                     |
+| `pnpm run audit:pnpm`      | Run audit of modules                             |
 
 ### Bun
 
@@ -129,6 +132,7 @@ All commands are run from the root of the project, from a terminal:
 | `bun run preview`         | Preview build locally, before creating output    |
 | `bun run astro ...`       | Run CLI commands like `astro add`, `astro check` |
 | `bun run astro -- --help` | Get help using the Astro CLI                     |
+| `bun run audit:bun`       | Run audit of modules                             |
 
 ### Deno
 
@@ -141,6 +145,7 @@ All commands are run from the root of the project, from a terminal:
 | `deno run preview`         | Preview build locally, before creating output    |
 | `deno run astro ...`       | Run CLI commands like `astro add`, `astro check` |
 | `deno run astro -- --help` | Get help using the Astro CLI                     |
+| `deno run audit:deno`      | Run audit of modules                             |
 
 ## Getting Started
 Delete the demo application under the ```src``` folder and being to build your own application. 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "create-outsystems-astro",
   "type": "module",
-  "version": "0.4.2",
+  "version": "0.5.0",
   "description": "Create an OutSystems Astro Island project to import as a component into your OutSystems application",
   "repository": {
     "type": "git",

package/template/.prettierignore

@@ -1,5 +1,6 @@
 .github/
 bun.lock
+deno.json
 deno.lock
 dist/
 node_modules/
@@ -8,4 +9,4 @@ package-lock.json
 package.json
 patches/
 pnpm-lock.yaml
-yarn.lock
+yarn.lock

package/template/AGENTS.md

@@ -24,6 +24,10 @@
 - The project can intialized from the Create OutSystems Astro package (https://www.npmjs.com/package/create-outsystems-astro).
 - In this document, for any reference to running package manager script, the `PM` attribute should be replaced with whatever package manager the user is using.
 
+In OutSystems 11, the Islands library is available at https://www.outsystems.com/forge/component-overview/22857/islands-o11.
+
+In OutSystems Developer Cloud, the Islands library is available at https://www.outsystems.com/forge/component-overview/22960/islands-odc.
+
 ### Pages
 
 - The files in src/pages/\*.astro are used as a starting point and holds the components for generation. They can be tested by running `npm run dev`. That will show what the component looks like as rendered. The sample example pages are broken out by framework name (src/pages/react, src/pages/vue, etc). This page will house the component(s) entry points.
@@ -34,12 +38,12 @@
 
 ### Components
 
-- The components live in the folder framework/[NAME]/ (src/framework/angular, src/framework/react and src/framework/vue ) with each framework having its own folder. The framework folder should stay in place as the components will be rendered from there. The Angular components will only be transformed by Astro if they are in the framework/angular folder.
+- The components live in the folder framework/{NAME}/ (src/framework/angular, src/framework/react and src/framework/vue ) with each framework having its own folder. The framework folder should stay in place as the components will be rendered from there. The Angular components will only be transformed by Astro if they are in the framework/angular folder.
 
 ### Parameters
 
 - Parameters are assigned as attributes on the component. Each framework will then handle them as incoming parameters.
-- OutSystems will pass in parameters already prepared for the ``<astro-island>`. It already has copied the Astro method of serialization in https://github.com/withastro/astro/blob/main/packages/astro/src/runtime/server/serialize.ts.
+- OutSystems will pass in parameters already prepared for the astro-island. It already has copied the Astro method of serialization in https://github.com/withastro/astro/blob/main/packages/astro/src/runtime/server/serialize.ts.
 
 #### Slots
 
@@ -126,12 +130,61 @@ the slots can be used as:
 
 Angular does not support the use of slots. Any use of slots with Angular should be discouraged.
 
+### Nano Stores
+
+The Nano Stores library - https://github.com/nanostores/nanostores - is supported for both sharing state between different Islands or from OutSystems to an Island. This could be used in place of a parameter, but parameters should be the default method.
+
+The current supported OutSystems Nano Stores module only suports Atoms and Maps. It can either subscribe to an Atom or Map. It can also listen to Keys of a Map.
+
+The OutSystems 11 library is called Lightweight State Manager - https://www.outsystems.com/forge/component-overview/23528/lightweight-state-manager-o11 is available in the O11 Forge.
+
+The OutSystems Developer Cloud library is called Lightweight State Manager and is available in the ODC Forge.
+
+Nano Stores are currently supported for only React - https://github.com/nanostores/react and Vue - https://github.com/nanostores/vue. The Angular 21 library does not yet support them.
+
+In OutSystems, the store will be on the Window object. The Islands component will then have to access it from there.
+
+#### React
+
+```js
+import { useStore } from "@nanostores/react";
+import { useState } from "react";
+
+export default function Counter({}) {
+  const nanoStoreValue = useStore(window.Stores["MyGreatStore"]);
+
+  return (
+    <>
+      <div>
+        <strong>Nano Store value:</strong>
+        <div>{nanoStoreValue}</div>
+      </div>
+    </>
+  );
+}
+```
+
+#### Vue
+
+```vue
+<script setup lang="ts">
+import { useStore } from "@nanostores/vue";
+const nanoStoreValue = useStore(window.Stores["MyGreatStore"]);
+</script>
+
+<template>
+  <div>
+    <div>{{ nanoStoreValue }}</div>
+  </div>
+</template>
+```
+
 ### Testing
 
 - There is a preset set of testing tools, but can be changed after generation.
 - The unit testing library setup is Vitest. The unit tests are located in `test/unit` folder.
-- The integration testing library is Testing Library with an equivalent library per framework. Each framework is in its own folder in `test/integration/[FRAMEWORK]`.
-- The end-to-end testing library is Playwright. Each framework is in its own folder in `test/e2e/[FRAMEWORK]`.
+- The integration testing library is Testing Library with an equivalent library per framework. Each framework is in its own folder in `test/integration/{FRAMEWORK}`.
+- The end-to-end testing library is Playwright. Each framework is in its own folder in `test/e2e/{FRAMEWORK}`.
 
 ### Linting and formatting
 
@@ -143,7 +196,7 @@ Angular does not support the use of slots. Any use of slots with Angular should
 
 ### Handlers
 
-- Incoming functions from OutSystems cannot be passed as function handlers. The way that OutSystems will invoke them is by binding the function with the name to the `document` object of the page. Then it will pass in that name as a parameter. For example, if you need a function handler of `ShowMessage`, it will need to be called as `document[ShowMessage]`.
+- Incoming functions from OutSystems cannot be passed as function handlers. The way that OutSystems will invoke them is by binding the function with the name to the `window` object of the page. Then it will pass in that name as a parameter. For example, if you need a function handler of `ShowMessage`, it will need to be called as `window[ShowMessage]`.
 - Passing in basic text, number and boolean should be fine to the handler. Any array or object must be JSON stringified prior to being passed into the handler.
 
 ## Generating output