The ESM standard is considered stable in NodeJS and well supported by a lot of modern JavaScript tools.
ESLint does a good job validating and fixing ESM code (as long as you don't use top-level await, coming in ESLint v8). Make sure to enable the latest ECMA features in the ESLint config.
{
Link: https://docs.papermc.io/paper/anti-xray
Help: https://discord.gg/papermc
Anti-Xray can be configured per world in the paper.yml configuration file. To understand how per world configuration works please read this first. Note that after changing any settings for Anti-Xray you have to restart your server. Executing the /reload command (you should never do this) won't apply the settings to worlds that are already loaded.
| Prefix | Description | Notes | |
|---|---|---|---|
| ac_ | Platform Client ID | Identifier for an auth code/client id. | |
| acct_ | Account ID | Identifier for an Account object. | |
| aliacc_ | Alipay Account ID | Identifier for an Alipay account. | |
| ba_ | Bank Account ID | Identifier for a Bank Account object. | |
| btok_ | Bank Token ID | Identifier for a Bank Token object. | |
| card_ | Card ID | Identifier for a Card object. | |
| cbtxn_ | Customer Balance Transaction ID | Identifier for a Customer Balance Transaction object. | |
| ch_ | Charge ID | Identifier for a Charge object. | |
| cn_ | Credit Note ID | Identifier for a Credit Note object. |
Deploy key is a SSH key set in your repo to grant client read-only (as well as r/w, if you want) access to your repo.
As the name says, its primary function is to be used in the deploy process in replace of username/password, where only read access is needed. Therefore keep the repo safe from the attack, in case the server side is fallen.
