Move of SelfHostedApplicationFactory to @cartesi/rollups

[tuler]

More changes of moving SelfHostedApplicationFactory to @cartesi/rollups

Also removes more "sunodo" terms.

[changeset-bot[bot]]

🦋 Changeset detected

Latest commit: d04aaa458d400c8a2c07e5a9ddd119384638b222

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

| Name | Type | | ----------------- | ----- | | @sunodo/contracts | Minor | | @sunodo/web | Minor |

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 23, 2024 4:21pm
www	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 23, 2024 4:21pm

[socket-security[bot]]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/bytes@3.1.2	None	0	12.3 kB	dougwilson
npm/clsx@2.1.0	None	0	8.46 kB	lukeed
npm/copyfiles@2.4.1	filesystem Transitive: environment	+28	807 kB	cwmma
npm/fs-extra@11.2.0	Transitive: environment, filesystem	+3	112 kB	ryanzim
npm/progress-stream@2.0.0	None	+1	12.9 kB	freeall
npm/react-dom@18.2.0	environment	+3	4.62 MB	gnoff
npm/react@18.2.0	environment	+2	337 kB	gnoff
npm/semver@7.6.0	None	+2	125 kB	npm-cli-ops
npm/tslib@2.6.2	None	0	84 kB	typescript-bot
npm/typescript@5.4.3	None	0	32.4 MB	typescript-bot

🚮 Removed packages: npm/@cartesi/rollups@1.3.0, npm/@cartesi/rollups@1.4.0, npm/@cartesi/util@6.2.0, npm/@changesets/cli@2.27.1, npm/@commander-js/extra-typings@12.0.1, npm/@ensdomains/ens-contracts@1.1.4, npm/@helia/unixfs@3.0.2, npm/@inquirer/confirm@3.1.1, npm/@inquirer/core@7.1.1, npm/@inquirer/input@2.1.1, npm/@inquirer/select@2.2.1, npm/@inquirer/type@1.2.1, npm/@mantine/code-highlight@7.7.0, npm/@mantine/core@7.7.0, npm/@mantine/form@7.7.0, npm/@mantine/hooks@7.7.0, npm/@next/bundle-analyzer@14.1.4, npm/@next/eslint-plugin-next@14.1.4, npm/@nomicfoundation/hardhat-verify@2.0.6, npm/@nomicfoundation/hardhat-viem@2.0.1, npm/@oclif/core@3.26.0, npm/@oclif/plugin-help@6.0.20, npm/@oclif/plugin-plugins@5.0.1, npm/@oclif/test@3.2.8, npm/@openzeppelin/contracts@4.9.3, npm/@openzeppelin/contracts@5.0.2, npm/@rainbow-me/rainbowkit@2.0.2, npm/@safe-global/safe-singleton-factory@1.0.23, npm/@storybook/addon-essentials@8.0.4, npm/@storybook/addon-interactions@8.0.4, npm/@storybook/addon-links@8.0.4, npm/@storybook/blocks@8.0.4, npm/@storybook/nextjs@8.0.4, npm/@storybook/preview-api@8.0.4, npm/@storybook/react@8.0.4, npm/@storybook/test@8.0.4, npm/@sunodo/wagmi-plugin-hardhat-deploy@0.3.0, npm/@tabler/icons-react@3.1.0, npm/@tanstack/react-query@5.28.8, npm/@types/bytes@3.1.4, npm/@types/chai@4.3.14, npm/@types/fs-extra@11.0.4, npm/@types/inquirer@9.0.7, npm/@types/mocha@10.0.6, npm/@types/node-fetch@2.6.11, npm/@types/node@20.11.30, npm/@types/progress-stream@2.0.5, npm/@types/prompts@2.4.9, npm/@types/react-dom@18.2.22, npm/@types/react@18.2.71, npm/@types/semver@7.5.8, npm/@types/tmp@0.2.6

View full report↗︎

[socket-security[bot]]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Install scripts	npm/esbuild@0.19.12	Install script: postinstall Source: node install.js	orphan: npm/esbuild@0.19.12

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/esbuild@0.19.12

[tuler]

LGTM

Should we worry about the Socket security report, or can that be handled on another PR before release?

I'll handle the Socket security report when we get to stability of the transition