fix: multi return

This commit is contained in:
2025-06-04 04:33:40 +09:00
parent 927ba37a71
commit 3b7913ce19
4 changed files with 8 additions and 4 deletions

View File

@@ -1,6 +1,6 @@
{ {
"name": "computercraft-ts", "name": "computercraft-ts",
"version": "1.0.9", "version": "1.0.10",
"description": "", "description": "",
"license": "ISC", "license": "ISC",
"author": "", "author": "",
@@ -13,6 +13,7 @@
}, },
"devDependencies": { "devDependencies": {
"@eslint/js": "^9.27.0", "@eslint/js": "^9.27.0",
"@typescript-to-lua/language-extensions": "^1.19.0",
"eslint": "^9.27.0", "eslint": "^9.27.0",
"globals": "^16.2.0", "globals": "^16.2.0",
"luamin": "^1.0.4", "luamin": "^1.0.4",

3
pnpm-lock.yaml generated
View File

@@ -11,6 +11,9 @@ importers:
'@eslint/js': '@eslint/js':
specifier: ^9.27.0 specifier: ^9.27.0
version: 9.28.0 version: 9.28.0
'@typescript-to-lua/language-extensions':
specifier: ^1.19.0
version: 1.19.0
eslint: eslint:
specifier: ^9.27.0 specifier: ^9.27.0
version: 9.28.0 version: 9.28.0

View File

@@ -7,7 +7,7 @@
"strict": true, "strict": true,
"plugins": [{ "name": "typescript-tstl-plugin" }], "plugins": [{ "name": "typescript-tstl-plugin" }],
"outDir": "dist", "outDir": "dist",
"types": ["./types/index"], "types": ["./types/index", "@typescript-to-lua/language-extensions"],
"noImplicitAny": false "noImplicitAny": false
}, },
"tstl": { "tstl": {

4
types/index.d.ts vendored
View File

@@ -5,7 +5,7 @@
* Based on documentation from https://tweaked.cc/ * Based on documentation from https://tweaked.cc/
*/ */
export { }; export {};
/** @noSelf **/ /** @noSelf **/
declare global { declare global {
@@ -241,7 +241,7 @@ declare global {
function receive( function receive(
protocolFilter?: string, protocolFilter?: string,
timeout?: number, timeout?: number,
): [number, RednetData, string | null] | null; ): LuaMultiReturn<[number, RednetData, string | null]> | null;
/** /**
* Register the system as "hosting" the desired protocol under the specified name. If a rednet lookup is performed for that protocol (and maybe name) on the same network, the registered system will automatically respond via a background process, hence providing the system performing the lookup with its ID number. * Register the system as "hosting" the desired protocol under the specified name. If a rednet lookup is performed for that protocol (and maybe name) on the same network, the registered system will automatically respond via a background process, hence providing the system performing the lookup with its ID number.