Sonarly Claude Code
58a799251c
https://sonarly.com/issue/33657?type=bug Tarball-deployed application logos and screenshots render as broken images (404) because the tarball upload path stores the raw SDK-relative manifest path (e.g. `public/linear-logomark.svg`) without resolving it to an absolute URL, unlike the NPM and dev paths which call `resolveManifestAssetUrls()`. Fix: **Problem:** Tarball-deployed application logos render as broken images because the tarball upload path stores the raw SDK-relative manifest path (e.g. `public/linear-logomark.svg`) in the application registration, and the install service copies this raw path to the `application.logo` column without resolving it to an absolute URL. The NPM and dev paths both call `resolveManifestAssetUrls()` to convert relative paths to absolute URLs, but the install-time sync path does not. **Fix (2 files):** 1. **`application-sync.service.ts`** — In the `syncApplication` method (called for all deploy paths: NPM, dev, tarball), resolve the manifest's asset URLs to absolute server URLs before storing `logo` on the install record. This uses the same `resolveManifestAssetUrls` utility already used by the NPM catalog sync and dev resolver, with the same URL pattern (`<SERVER_URL>/public-assets/<workspaceId>/<applicationId>/<filePath>`). The utility safely preserves already-absolute URLs, so NPM apps with CDN URLs are unaffected. 2. **`SettingsApplicationDetails.tsx`** — Reorder the logo resolution fallback chain so `application?.logo` (the resolved install-record URL) takes precedence over `app?.logoUrl` (the raw manifest path from the shared registration). Previously `app?.logoUrl` won first, which for tarball apps contained the unresolved raw path. This implements Option A from the issue: resolve at install time, store on the install record. It's the minimal fix that addresses the immediate user-visible bug (broken logos for tarball-deployed apps) while being safe for all existing deploy paths. **Not addressed (acknowledged out of scope in the issue):** - Screenshots from tarball manifests still have raw paths (would need a new column or a `@ResolveField` — Option B from the issue) - The dev path still bakes workspace-scoped URLs into the shared registration manifest (harmless in single-workspace dev, but architecturally incorrect) - Pre-install marketplace browse page still shows raw paths for tarball apps (needs Option C — registration-scoped public assets)
The #1 Open-Source CRM
Website · 
Documentation · 
Roadmap · 
Discord · 
Figma
Why Twenty
Twenty gives technical teams the building blocks for a custom CRM that meets complex business needs and quickly adapts as the business evolves. Twenty is the CRM you build, ship, and version like the rest of your stack.
Learn more about why we built Twenty
Installation
Cloud
The fastest way to get started. Sign up at twenty.com and spin up a workspace in under a minute, with no infrastructure to manage and always up to date.
Build an app
Scaffold a new app with the Twenty CLI:
npx create-twenty-app my-app
Define objects, fields, and views as code:
import { defineObject, FieldType } from 'twenty-sdk/define';
export default defineObject({
nameSingular: 'deal',
namePlural: 'deals',
labelSingular: 'Deal',
labelPlural: 'Deals',
fields: [
{ name: 'name', label: 'Name', type: FieldType.TEXT },
{ name: 'amount', label: 'Amount', type: FieldType.CURRENCY },
{ name: 'closeDate', label: 'Close Date', type: FieldType.DATE_TIME },
],
});
Then ship it to your workspace:
npx twenty deploy
See the app development guide for objects, views, agents, and logic functions.
Self-hosting
Run Twenty on your own infrastructure with Docker Compose, or contribute locally via the local setup guide.
Everything you need
Twenty gives you the building blocks of a modern CRM (objects, views, workflows, and agents) and lets you extend them as code. Here's a tour of what's in the box.
Want to go deeper? Read the 
User Guide for product walkthroughs, or the Documentation for developer reference.
|
|
|
|
|
|
Learn more about version control in docStack
TypeScript
Nx
NestJS, with BullMQ, 
PostgreSQL, 
Redis
React, with Jotai, Linaria and Lingui
Thanks
Thanks to these amazing services that we use and recommend for UI testing (Chromatic), code review (Greptile), catching bugs (Sentry) and translating (Crowdin).
Join the Community
Star the repo · Discord · 
Feature requests · Releases · 
X · 
LinkedIn · 
Crowdin · 
Contribute