mirror of
https://github.com/bitburner-official/bitburner-src.git
synced 2026-04-17 14:59:16 +02:00
dcd2f33f7c
* Update api-documentor and api-extractor. #1566 follow-up.
I have verified that the HTML/markdown table generation bug in
[#4878](https://github.com/microsoft/rushstack/issues/4878) in rushstack
for api-documentor has been fixed as per rushstack#5256. The testcase
[repro](https://github.com/catloversg/api-documenter-bug-pr-4578) now
produces the correct expected output.
I have confirmed that the generated output in bitburner from
`npm run doc` now generated HTML tables, and correctly inserts
a blank line between the </table> and the follow line (e.g. Returns).
Stylisticly it could use some whitespace, but it is correctly rendered.
This commit is only the updated packages, not the updated generated
documentation. I assume that is automatically generated by the GitHub
workflow.
* Follow up to 5f732a6f35, include `npm run doc` changed docs.
* Add missing license info
* Fix React warning
---------
Co-authored-by: CatLover <152669316+catloversg@users.noreply.github.com>
1.2 KiB
1.2 KiB
Home > bitburner > NS > writePort
NS.writePort() method
Write data to a port.
Signature:
writePort(portNumber: number, data: any): any;
Parameters
|
Parameter |
Type |
Description |
|---|---|---|
|
portNumber |
number |
Port to write to. Must be a positive integer. |
|
data |
any |
Data to write, it's cloned with structuredClone(). |
Returns:
any
The data popped off the queue if it was full, or null if it was not full.
Remarks
RAM cost: 0 GB
Write data to the given Netscript port.
There is a limit on the maximum number of ports, but you won't reach that limit in normal situations. If you do, it usually means that there is a bug in your script that leaks port data. A port is freed when it does not have any data in its underlying queue. ns.clearPort deletes all data on a port. ns.readPort reads the first element in the port's queue, then removes it from the queue.