@assinafy/piece-assinafy 0.1.0 → 0.1.1

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 0.1.1
+
+- The package's homepage, repository and issue links point to https://github.com/assinafy/activepieces.
+
 ## 0.1.0
 
 First release.

package/LICENSE

@@ -240,7 +240,7 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
-## es-object-atoms@1.1.1 (MIT)
+## es-object-atoms@1.1.2 (MIT)
 
 MIT License
 
@@ -452,30 +452,6 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
-## hasown@2.0.3 (MIT)
-
-MIT License
-
-Copyright (c) Jordan Harband and contributors
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
 ## hasown@2.0.4 (MIT)
 
 MIT License

package/README.md

@@ -183,18 +183,18 @@ Document outputs:
 
 ## Development
 
-The piece lives in the Activepieces monorepo at `packages/pieces/community/assinafy`. Requirements: Node.js 24 LTS and Bun.
+Requirements: Node.js 24 LTS and Git.
 
 ```sh
-bun install
-npx turbo run build --filter=@assinafy/piece-assinafy
-npx turbo run lint --filter=@assinafy/piece-assinafy
-cd packages/pieces/community/assinafy
+npm install              # also downloads the Activepieces libraries
 npm run typecheck        # source and tests
 npm test                 # unit tests, no network
 npm run test:coverage    # with coverage thresholds
+npm run build            # bundles the piece into dist/
 ```
 
+The piece is built against the Activepieces piece framework at the commit in `ACTIVEPIECES_REF`. `npm install` downloads the framework, common and core libraries from that commit into `.activepieces/`, and the build bundles them into a single file. To build against a newer Activepieces, change `ACTIVEPIECES_REF`, run `npm install` and run the tests.
+
 Unit tests mock the HTTP client and block any real network request. One upload test runs the real Activepieces HTTP client against a stubbed `fetch` to check the multipart request on the wire.
 
 ### Implementation notes
@@ -230,35 +230,28 @@ ASSINAFY_API_KEY=<sandbox key> npm run test:live
 
 The suite also reads a document's activity log, which **Document Signed** relies on.
 
-### Try it in a local Activepieces
+### Try it in Activepieces
 
-Add `AP_DEV_PIECES=assinafy` to `packages/server/api/.env`, run `npm start` from the repository root and open <http://localhost:4200>.
+Run `npm run build`, then `npm pack ./dist` to create a `.tgz` file. In Activepieces, open **Setup → Pieces** in the platform admin, click **Install Piece**, choose **Packed Archive (.tgz)** and upload the file.
 
 ### Translations
 
 `src/i18n/translation.json` is generated from the piece and `src/i18n/pt.json` holds the Brazilian Portuguese strings. After changing any display name, description or option label:
 
 ```sh
-npm run cli -- pieces generate-translation-file assinafy
+npm run translations
 ```
 
-If the command stops on a type error outside this piece, run it as `TS_NODE_TRANSPILE_ONLY=true npm run cli -- pieces generate-translation-file assinafy`. Then update `pt.json`. The tests fail while either file is out of date.
+Then update `pt.json`. The tests fail while either file is out of date.
 
 Activepieces does not translate the connection dialog of a piece with more than one connection type, so the dialog is shown in English.
 
 ### Publishing
 
 1. Bump `version` in `package.json` (patch for new actions, optional inputs and fixes; major for removals, new required inputs or changed behavior) and add the release to `CHANGELOG.md`.
-2. Run `npm run licenses` in this folder. It rewrites `LICENSE` with the license of every package bundled into the published file.
-3. Sign in to npm (`npm login`) with an account that can publish to the `@assinafy` scope.
-4. From the repository root:
-
-   ```sh
-   TS_NODE_TRANSPILE_ONLY=true npm_config_dry_run=true npm run publish-piece assinafy   # check the package, publishes nothing
-   TS_NODE_TRANSPILE_ONLY=true npm run publish-piece assinafy
-   ```
-
-   `TS_NODE_TRANSPILE_ONLY=true` skips an unrelated type error elsewhere in the repository that stops the script. The script builds the piece, bundles it into a single file with the Activepieces libraries inlined, checks that no workspace or `@activepieces/*` dependency is left, and publishes it with public access together with the READMEs, `LICENSE` and `CHANGELOG.md`. It skips a version that is already on npm, so bump the version before publishing changes.
+2. Run `npm run licenses`. It rewrites `LICENSE` with the license of every package bundled into the published file.
+3. Check the package with `npm run build && npm publish ./dist --dry-run`.
+4. Commit, push to `main`, and push a `piece-assinafy-vX.Y.Z` tag that matches the version. The **Publish Assinafy piece** workflow typechecks, tests and builds the piece, then publishes it to npm through trusted publishing, together with the READMEs, `LICENSE` and `CHANGELOG.md`.
 
 Never rename an action, trigger or input after release: flows reference them by name.
 

package/README.pt-BR.md

@@ -183,18 +183,18 @@ Saídas de **Novo Evento (Instantâneo)**:
 
 ## Desenvolvimento
 
-A peça fica no monorepo do Activepieces em `packages/pieces/community/assinafy`. Requisitos: Node.js 24 LTS e Bun.
+Requisitos: Node.js 24 LTS e Git.
 
 ```sh
-bun install
-npx turbo run build --filter=@assinafy/piece-assinafy
-npx turbo run lint --filter=@assinafy/piece-assinafy
-cd packages/pieces/community/assinafy
+npm install              # também baixa as bibliotecas do Activepieces
 npm run typecheck        # código e testes
 npm test                 # testes unitários, sem rede
 npm run test:coverage    # com limites de cobertura
+npm run build            # gera o pacote da peça em dist/
 ```
 
+A peça é compilada com o framework de peças do Activepieces no commit indicado em `ACTIVEPIECES_REF`. O `npm install` baixa as bibliotecas framework, common e core desse commit para `.activepieces/`, e o build as embute em um único arquivo. Para compilar com um Activepieces mais recente, altere o `ACTIVEPIECES_REF`, execute `npm install` e rode os testes.
+
 Os testes unitários simulam o cliente HTTP e bloqueiam qualquer acesso real à rede. Um teste de envio usa o cliente HTTP real do Activepieces com um `fetch` simulado para verificar a requisição multipart enviada.
 
 ### Notas de implementação
@@ -230,35 +230,28 @@ ASSINAFY_API_KEY=<chave do sandbox> npm run test:live
 
 O conjunto também lê o histórico de atividades de um documento, do qual **Documento Assinado** depende.
 
-### Testar em um Activepieces local
+### Testar no Activepieces
 
-Adicione `AP_DEV_PIECES=assinafy` em `packages/server/api/.env`, execute `npm start` na raiz do repositório e abra <http://localhost:4200>.
+Execute `npm run build` e depois `npm pack ./dist` para gerar um arquivo `.tgz`. No Activepieces, abra **Setup → Pieces** na administração da plataforma, clique em **Install Piece**, escolha **Packed Archive (.tgz)** e envie o arquivo.
 
 ### Traduções
 
 `src/i18n/translation.json` é gerado a partir da peça e `src/i18n/pt.json` contém os textos em português do Brasil. Depois de alterar qualquer nome, descrição ou rótulo de opção:
 
 ```sh
-npm run cli -- pieces generate-translation-file assinafy
+npm run translations
 ```
 
-Se o comando parar em um erro de tipos fora desta peça, execute `TS_NODE_TRANSPILE_ONLY=true npm run cli -- pieces generate-translation-file assinafy`. Depois atualize o `pt.json`. Os testes falham enquanto algum dos dois arquivos estiver desatualizado.
+Depois atualize o `pt.json`. Os testes falham enquanto algum dos dois arquivos estiver desatualizado.
 
 O Activepieces não traduz a janela de conexão de uma peça com mais de um tipo de conexão, então essa janela aparece em inglês.
 
 ### Publicação
 
 1. Aumente a `version` no `package.json` (patch para novas ações, entradas opcionais e correções; major para remoções, novas entradas obrigatórias ou mudança de comportamento) e registre a versão no `CHANGELOG.md`.
-2. Execute `npm run licenses` nesta pasta. Ele reescreve o `LICENSE` com a licença de cada pacote embutido no arquivo publicado.
-3. Autentique-se no npm (`npm login`) com uma conta que possa publicar no escopo `@assinafy`.
-4. Na raiz do repositório:
-
-   ```sh
-   TS_NODE_TRANSPILE_ONLY=true npm_config_dry_run=true npm run publish-piece assinafy   # confere o pacote, não publica nada
-   TS_NODE_TRANSPILE_ONLY=true npm run publish-piece assinafy
-   ```
-
-   `TS_NODE_TRANSPILE_ONLY=true` ignora um erro de tipos não relacionado em outra parte do repositório que interrompe o script. O script compila a peça, gera um único arquivo com as bibliotecas do Activepieces embutidas, verifica que não sobrou nenhuma dependência de workspace ou `@activepieces/*` e publica com acesso público junto com os READMEs, o `LICENSE` e o `CHANGELOG.md`. Uma versão que já está no npm é ignorada, então aumente a versão antes de publicar alterações.
+2. Execute `npm run licenses`. Ele reescreve o `LICENSE` com a licença de cada pacote embutido no arquivo publicado.
+3. Confira o pacote com `npm run build && npm publish ./dist --dry-run`.
+4. Faça o commit, envie para a `main` e envie uma tag `piece-assinafy-vX.Y.Z` igual à versão. O workflow **Publish Assinafy piece** verifica os tipos, roda os testes, gera o pacote e o publica no npm por trusted publishing, junto com os READMEs, o `LICENSE` e o `CHANGELOG.md`.
 
 Nunca renomeie uma ação, gatilho ou entrada depois de publicada: os fluxos os referenciam pelo nome.
 

package/package.json

@@ -1,17 +1,16 @@
 {
   "name": "@assinafy/piece-assinafy",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Activepieces piece for Assinafy electronic signatures.",
   "license": "MIT",
   "author": "Assinafy",
-  "homepage": "https://github.com/assinafy/activepieces/tree/main/packages/pieces/community/assinafy#readme",
+  "homepage": "https://github.com/assinafy/activepieces#readme",
   "bugs": {
     "url": "https://github.com/assinafy/activepieces/issues"
   },
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/assinafy/activepieces.git",
-    "directory": "packages/pieces/community/assinafy"
+    "url": "git+https://github.com/assinafy/activepieces.git"
   },
   "keywords": [
     "activepieces",
@@ -23,11 +22,10 @@
   "dependencies": {},
   "files": [
     "src/index.js",
-    "package.json",
     "src/i18n",
-    "CHANGELOG.md",
-    "LICENSE",
     "README.md",
-    "README.pt-BR.md"
+    "README.pt-BR.md",
+    "CHANGELOG.md",
+    "LICENSE"
   ]
-}
+}