MORPH
SIGN IN SIGN UP
HeyPuter / puter UNCLAIMED

🌐 The Internet Computer! Free, Open-Source, and Self-Hostable.

40066 0 1 JavaScript
Normal View History Raw
Initial commit
2024-03-02 18:39:14 -08:00
{
"name": "puter.com",
release: 2.5.1
2025-02-13 21:50:39 -05:00
"version": "2.5.1",
Initial commit
2024-03-02 18:39:14 -08:00
"author": "Puter Technologies Inc.",
"license": "AGPL-3.0-only",
"description": "Desktop environment in the browser!",
"homepage": "https://puter.com",
Migrate to JavaScript modules
2024-03-20 14:10:39 +00:00
"type": "module",
Release backend
2024-03-30 19:08:03 -04:00
"main": "exports.js",
Initial commit
2024-03-02 18:39:14 -08:00
"directories": {
"lib": "lib"
},
"devDependencies": {
feat: add expiry support to DBKV, and eslint config
2025-09-09 18:45:44 -07:00
"@eslint/js": "^9.35.0",
fix: eslint autofixable errors (#2002)
2025-11-21 13:22:19 -08:00
"@playwright/test": "^1.56.1",
feat: add expiry support to DBKV, and eslint config
2025-09-09 18:45:44 -07:00
"@stylistic/eslint-plugin": "^5.3.1",
feat: refactor ai to have single entry point and follow defined model structure (#2114) * feat: refactor ai to have single entry point and follow defined model structure * fix: missing openrouter registration * fix: dedupe models * feat: provide usage in stream mode :rocket:
2025-12-09 15:59:21 -08:00
"@types/mime-types": "^3.0.1",
ci: init e2e test for browser env, tidy other tests (#1796) * ci: init e2e test for browser env stash changes * test: update fsentry definition, add tests stash changes * test: pass puter-js mkdir test * test: add test for puter-js move * tidy code * tidy code * doc: add docs for playwright test * recover memoryfs * test: puter-js readdir/stat * test: puter-js write * test: puter-js read * test: puter-js move_cart * test: fix failed tests on move * tests: rename files * test: puter-js copy_cart * tests: puter-js batch/delete, read config from file * ci: add vitest * ci: update names and timeout * ci: simplify playwright-test * ci: simplify api-test * move "api-tester" from tools to tests * test: update example config * test: remove folder tests/api-tester/ci * test: unify config location * test: remove unused files * ci: fix wrong config * ci: fix wrong path * test: add docs * ci: update timeout, print artifact url
2025-10-28 16:35:37 -07:00
"@types/uuid": "^10.0.0",
feat: metering service allowence checks and subscription integration 🚀 (#1749) * feat: metering allowence checks * fix: bad math
2025-10-15 02:28:25 -07:00
"@typescript-eslint/eslint-plugin": "^8.46.1",
"@typescript-eslint/parser": "^8.46.1",
Manual package updates, `npm audit --force`, etc (#2669) * chore: upgrade git-date (used for release notes generator) * chore: update vitest, vitest plugins, and svgo * chore: run `npm audit fix` * chore: run `npm audit --force` * meta: empty commit to run git tests * fix: tests gone because of a... syntax error? I question GitHub's judgement of handling a syntax error in the file that defines tests to run on PRs by pretending everything is fine and passing all PRs. That to me seems like the worst possible way to handle that. I think they should have done it not like that.
2026-03-17 12:43:17 -07:00
"@vitest/coverage-v8": "^4.1.0",
"@vitest/ui": "^4.1.0",
Initial commit
2024-03-02 18:39:14 -08:00
"chalk": "^4.1.0",
"clean-css": "^5.3.2",
Implement .env support for PORT property
2024-03-12 22:42:13 -07:00
"dotenv": "^16.4.5",
feat: add expiry support to DBKV, and eslint config
2025-09-09 18:45:44 -07:00
"eslint": "^9.35.0",
lint: configure eslint not operator spacing The styleguide for Puter's backend expects spaces after top-level not operators inside conditions. This commit adds an AI-generated eslint plugin and, since it conflicts with the existing space-unary-ops plugin from stylistic, also adds a wrapped version of space-unary-ops that ignores top-level not operators so that this plugin will work as expected.
2025-11-05 15:17:59 -05:00
"eslint-rule-composer": "^0.3.0",
Initial commit
2024-03-02 18:39:14 -08:00
"express": "^4.18.2",
feat: DAV Locks support + refactor of DAV method handler (#1486) * feat: DAV Locks support + refactor of DAV method handler * format: Restore old whitespace for CoreModule.js * fix: options route registering after likecycle hooks --------- Co-authored-by: Neal Shah <30693865+ProgrammerIn-wonderland@users.noreply.github.com>
2025-09-26 08:00:29 -07:00
"globals": "^15.15.0",
Implement .env support for PORT property
2024-03-12 22:42:13 -07:00
"html-entities": "^2.3.3",
fix: html-webpack-plugin dev dep
2024-09-04 23:51:57 -04:00
"html-webpack-plugin": "^5.6.0",
devex: make it impossible to commit eslint errors
2025-09-24 17:41:48 -04:00
"husky": "^9.1.7",
chore: add missing license headers
2024-07-09 04:10:33 -04:00
"license-check-and-add": "^4.0.5",
Manual package updates, `npm audit --force`, etc (#2669) * chore: upgrade git-date (used for release notes generator) * chore: update vitest, vitest plugins, and svgo * chore: run `npm audit fix` * chore: run `npm audit --force` * meta: empty commit to run git tests * fix: tests gone because of a... syntax error? I question GitHub's judgement of handling a syntax error in the file that defines tests to run on PRs by pretending everything is fine and passing all PRs. That to me seems like the worst possible way to handle that. I think they should have done it not like that.
2026-03-17 12:43:17 -07:00
"mocha": "^7.2.0",
Release backend
2024-03-30 19:08:03 -04:00
"nodemon": "^3.1.0",
Manual package updates, `npm audit --force`, etc (#2669) * chore: upgrade git-date (used for release notes generator) * chore: update vitest, vitest plugins, and svgo * chore: run `npm audit fix` * chore: run `npm audit --force` * meta: empty commit to run git tests * fix: tests gone because of a... syntax error? I question GitHub's judgement of handling a syntax error in the file that defines tests to run on PRs by pretending everything is fine and passing all PRs. That to me seems like the worst possible way to handle that. I think they should have done it not like that.
2026-03-17 12:43:17 -07:00
"simple-git": "^3.32.3",
ci: init e2e test for browser env, tidy other tests (#1796) * ci: init e2e test for browser env stash changes * test: update fsentry definition, add tests stash changes * test: pass puter-js mkdir test * test: add test for puter-js move * tidy code * tidy code * doc: add docs for playwright test * recover memoryfs * test: puter-js readdir/stat * test: puter-js write * test: puter-js read * test: puter-js move_cart * test: fix failed tests on move * tests: rename files * test: puter-js copy_cart * tests: puter-js batch/delete, read config from file * ci: add vitest * ci: update names and timeout * ci: simplify playwright-test * ci: simplify api-test * move "api-tester" from tools to tests * test: update example config * test: remove folder tests/api-tester/ci * test: unify config location * test: remove unused files * ci: fix wrong config * ci: fix wrong path * test: add docs * ci: update timeout, print artifact url
2025-10-28 16:35:37 -07:00
"ts-proto": "^2.8.0",
feat: meter open ai (#1703) * feat: meter open ai * fix: dep injections & moderation * feat: add paging
2025-10-08 12:58:05 -07:00
"typescript": "^5.4.5",
Initial commit
2024-03-02 18:39:14 -08:00
"uglify-js": "^3.17.4",
Manual package updates, `npm audit --force`, etc (#2669) * chore: upgrade git-date (used for release notes generator) * chore: update vitest, vitest plugins, and svgo * chore: run `npm audit fix` * chore: run `npm audit --force` * meta: empty commit to run git tests * fix: tests gone because of a... syntax error? I question GitHub's judgement of handling a syntax error in the file that defines tests to run on PRs by pretending everything is fine and passing all PRs. That to me seems like the worst possible way to handle that. I think they should have done it not like that.
2026-03-17 12:43:17 -07:00
"vite-plugin-static-copy": "^3.3.0",
"vitest": "^4.1.0",
Implement .env support for PORT property
2024-03-12 22:42:13 -07:00
"webpack": "^5.88.2",
fix: eslint autofixable errors (#2002)
2025-11-21 13:22:19 -08:00
"webpack-cli": "^5.1.1",
"yaml": "^2.8.1"
Initial commit
2024-03-02 18:39:14 -08:00
},
"scripts": {
Remove terminal phoenix emulator (#2141) * Remove terminal and phoenix built-in apps and emulator This commit removes the terminal and phoenix built-in apps from the backend, database migrations, and permissions. It also deletes the entire emulator and phoenix/terminal app source directories, assets, and related configuration files. References to these apps in the backend module loader and router are removed, and related SQL migrations are updated to reflect their removal. * Remove emulator references from SelfHostedModule * Remove emulator integration and related references * Remove parsers and pty modules * Update package-lock.json
2025-12-11 16:53:21 -08:00
"test": "npx vitest run --config=src/backend/vitest.config.ts && node src/backend/tools/test.mjs",
test: vitest tests for puter js (#1693)
2025-10-06 15:00:40 -07:00
"test:puterjs-api": "vitest run tests/puterJsApiTests",
ci: add test coverage (#2073) * ci: add test coverage * ci: add test coverage
2025-12-01 08:56:44 -08:00
"test:backend": "npm run build:ts; vitest run --config=src/backend/vitest.config.ts",
"test:backend-coverage": "npm run build:ts; vitest run --config=src/backend/vitest.config.ts",
Release backend
2024-03-30 19:08:03 -04:00
"start=gui": "nodemon --exec \"node dev-server.js\" ",
feat: rawBody parser, user metadata column + other misc fixes (#1904)
2025-11-04 18:19:55 -08:00
"start": "node ./tools/run-selfhosted.js",
"prestart": "npm run build:ts",
devex: disable dev console by default, add socket
2025-10-14 16:56:35 -04:00
"dev": "npm run build:ts && DEVCONSOLE=1 node ./tools/run-selfhosted.js",
ci: mandatory eslint rules for build This commit adds verification for statically identifiable definite errors. Sometimes global variables used will be falsely reported as undefined variables in which case the new file `mandatory.eslint.config.js` should be updated to include these definitions in the narrowest scope possible that has these definitions
2025-11-20 21:22:44 -05:00
"build": "npx eslint --quiet -c eslint/mandatory.eslint.config.js src/backend/src extensions && npm run build:ts && cd src/gui && node ./build.js",
devex: make it impossible to commit eslint errors
2025-09-24 17:41:48 -04:00
"check-translations": "node tools/check-translations.js",
feat: meter open ai (#1703) * feat: meter open ai * fix: dep injections & moderation * feat: add paging
2025-10-08 12:58:05 -07:00
"prepare": "husky",
feat: refactor ai to have single entry point and follow defined model structure (#2114) * feat: refactor ai to have single entry point and follow defined model structure * fix: missing openrouter registration * fix: dedupe models * feat: provide usage in stream mode :rocket:
2025-12-09 15:59:21 -08:00
"build:ts": "tsc -p tsconfig.build.json",
ci: init e2e test for browser env, tidy other tests (#1796) * ci: init e2e test for browser env stash changes * test: update fsentry definition, add tests stash changes * test: pass puter-js mkdir test * test: add test for puter-js move * tidy code * tidy code * doc: add docs for playwright test * recover memoryfs * test: puter-js readdir/stat * test: puter-js write * test: puter-js read * test: puter-js move_cart * test: fix failed tests on move * tests: rename files * test: puter-js copy_cart * tests: puter-js batch/delete, read config from file * ci: add vitest * ci: update names and timeout * ci: simplify playwright-test * ci: simplify api-test * move "api-tester" from tools to tests * test: update example config * test: remove folder tests/api-tester/ci * test: unify config location * test: remove unused files * ci: fix wrong config * ci: fix wrong path * test: add docs * ci: update timeout, print artifact url
2025-10-28 16:35:37 -07:00
"gen": "./scripts/gen.sh"
Initial commit
2024-03-02 18:39:14 -08:00
},
Release backend
2024-03-30 19:08:03 -04:00
"workspaces": [
dev: add file walker
2024-07-09 03:15:42 -04:00
"src/*",
dev: add js-parse-and-output experiment
2024-07-09 03:40:34 -04:00
"tools/*",
"experiments/js-parse-and-output"
Release backend
2024-03-30 19:08:03 -04:00
],
Initial commit
2024-03-02 18:39:14 -08:00
"nodemonConfig": {
"ext": "js, json, mjs, jsx, svg, css",
"ignore": [
"./dist/",
"./node_modules/"
]
Release backend
2024-03-30 19:08:03 -04:00
},
"dependencies": {
chat_completions tool call fixes (#2434) * chat_completions tool call fixes * update chat completions test
2026-02-06 15:10:27 -08:00
"@ai-sdk/openai": "^3.0.25",
lint: configure eslint not operator spacing The styleguide for Puter's backend expects spaces after top-level not operators inside conditions. This commit adds an AI-generated eslint plugin and, since it conflicts with the existing space-unary-ops plugin from stylistic, also adds a wrapped version of space-unary-ops that ignores top-level not operators so that this plugin will work as expected.
2025-11-05 15:17:59 -05:00
"@anthropic-ai/sdk": "^0.68.0",
feat: dynamo in oss (#2195) * feat: dynamo in oss * fix: service name mismatch for dynamo client * fix: dynalite boot * fix: tests
2025-12-18 17:22:49 -08:00
"@aws-sdk/client-dynamodb": "^3.490.0",
AWS Secrets populator support
2025-08-29 20:30:06 -04:00
"@aws-sdk/client-secrets-manager": "^3.879.0",
Reapply "Logs Update" (#1730) This reverts commit 8f7a68ace605d746ef8505197ad7d380a91ec170.
2025-10-10 13:39:52 -04:00
"@aws-sdk/client-sns": "^3.907.0",
feat: dynamo in oss (#2195) * feat: dynamo in oss * fix: service name mismatch for dynamo client * fix: dynalite boot * fix: tests
2025-12-18 17:22:49 -08:00
"@aws-sdk/lib-dynamodb": "^3.490.0",
Reapply "feat: support Gemini imagegen service" This reverts commit 05071b43387022d5b5c5108325ba1d747353e0ca.
2025-09-12 19:16:58 -04:00
"@google/genai": "^1.19.0",
feat: enhanced ai command to perfom other commands (#1156) * Enhanced ai command to perfom other commands * Enhance AI Command in Puter's shell
2025-03-08 16:47:53 -06:00
"@heyputer/putility": "^1.0.2",
fix: install
2025-06-21 22:00:26 -04:00
"@paralleldrive/cuid2": "^2.2.2",
feat: DAV Locks support + refactor of DAV method handler (#1486) * feat: DAV Locks support + refactor of DAV method handler * format: Restore old whitespace for CoreModule.js * fix: options route registering after likecycle hooks --------- Co-authored-by: Neal Shah <30693865+ProgrammerIn-wonderland@users.noreply.github.com>
2025-09-26 08:00:29 -07:00
"@stylistic/eslint-plugin-js": "^4.4.1",
chat_completions tool call fixes (#2434) * chat_completions tool call fixes * update chat completions test
2026-02-06 15:10:27 -08:00
"ai": "^6.0.73",
fix: get event docs back in sync I used 'fix' for this instead of 'doc' because I am also adding a package for code that generates markdown, so this doesn't have the zero-risk nature typically associated with a "doc: " commit.
2025-02-25 17:52:54 -05:00
"dedent": "^1.5.3",
feat: dynamo in oss (#2195) * feat: dynamo in oss * fix: service name mismatch for dynamo client * fix: dynalite boot * fix: tests
2025-12-18 17:22:49 -08:00
"dynalite": "^4.0.0",
feat: DAV Locks support + refactor of DAV method handler (#1486) * feat: DAV Locks support + refactor of DAV method handler * format: Restore old whitespace for CoreModule.js * fix: options route registering after likecycle hooks --------- Co-authored-by: Neal Shah <30693865+ProgrammerIn-wonderland@users.noreply.github.com>
2025-09-26 08:00:29 -07:00
"express-xml-bodyparser": "^0.4.1",
Manual package updates, `npm audit --force`, etc (#2669) * chore: upgrade git-date (used for release notes generator) * chore: update vitest, vitest plugins, and svgo * chore: run `npm audit fix` * chore: run `npm audit --force` * meta: empty commit to run git tests * fix: tests gone because of a... syntax error? I question GitHub's judgement of handling a syntax error in the file that defines tests to run on PRs by pretending everything is fine and passing all PRs. That to me seems like the worst possible way to handle that. I think they should have done it not like that.
2026-03-17 12:43:17 -07:00
"file-type": "21.3.3",
dev: add human_readable_age to /whoami
2024-11-21 11:03:40 -05:00
"javascript-time-ago": "^2.5.11",
feat(backend): improve logger and reduce logs
2024-05-31 19:37:24 -04:00
"json-colorizer": "^3.0.1",
Manual package updates, `npm audit --force`, etc (#2669) * chore: upgrade git-date (used for release notes generator) * chore: update vitest, vitest plugins, and svgo * chore: run `npm audit fix` * chore: run `npm audit --force` * meta: empty commit to run git tests * fix: tests gone because of a... syntax error? I question GitHub's judgement of handling a syntax error in the file that defines tests to run on PRs by pretending everything is fine and passing all PRs. That to me seems like the worst possible way to handle that. I think they should have done it not like that.
2026-03-17 12:43:17 -07:00
"music-metadata": "11.12.3",
feat: automatically open the browser when starting Puter
2024-11-21 22:51:43 -08:00
"open": "^10.1.0",
Entri token service
2025-08-13 15:51:41 -04:00
"parse-domain": "^8.2.2",
Support configurable mod locations
2024-06-10 03:02:17 -04:00
"string-template": "^1.0.0",
Release backend
2024-03-30 19:08:03 -04:00
"uuid": "^9.0.1"
fix: make sharp optional
2025-07-04 18:29:29 -04:00
},
"optionalDependencies": {
Reapply "Logs Update" (#1730) This reverts commit 8f7a68ace605d746ef8505197ad7d380a91ec170.
2025-10-10 13:39:52 -04:00
"sharp": "^0.34.4",
fix: make sharp optional
2025-07-04 18:29:29 -04:00
"sharp-bmp": "^0.1.5",
"sharp-ico": "^0.1.5"
ci: drop support and testing for node 18
2025-09-18 16:08:19 -07:00
},
"engines": {
chore: update our required node version (#2204) * feat: fix broken queue bench * chore: update our required node version
2025-12-19 19:24:05 -08:00
"node": ">=24.0.0"
Revert "Created test cases for issue #878 "
2024-12-08 11:31:47 -08:00
}
ci: add test coverage (#2073) * ci: add test coverage * ci: add test coverage
2025-12-01 08:56:44 -08:00
}
Reference in New Issue Copy Permalink