Process completed with exit code 1.

Unable to process file command 'env' successfully.

Invalid value. Matching delimiter not found 'EOF'

error[markdown-order-section]: body has extra section(s) --> ERCS/erc-1363.md | 13 | ## Simple Summary | = help: see https://ethereum.github.io/eipw/markdown-order-section/

error[markdown-refs]: unable to read file `erc-677.md`: Io: JsValue(Error: ENOENT: no such file or directory, open 'ERCS/erc-677.md' Error: ENOENT: no such file or directory, open 'ERCS/erc-677.md') --> ERCS/erc-1363.md | 198 | This proposal has been inspired also by [ERC-223](https://github.com/ethereum/EIPs/issues/223) and [ERC-677](https://github.com/ethereum/EIPs/issues/677) but it uses the [ERC-721](./eip-721.md) approach, so it doesn't override the [ERC-20](./eip-20.md) `transfer` and `transferFrom` methods and defines the interfaces IDs to be implemented maintaining the [ERC-20](./eip-20.md) backwards compatibility. | = help: see https://ethereum.github.io/eipw/markdown-refs/

error[markdown-refs]: references to proposals with a `category` of `ERC` must use a prefix of `ERC` --> ERCS/erc-1363.md | 205 | One possible solution to mitigate this race condition is to first reduce the spender's allowance to 0 and set the desired value afterwards ([EIP-20#issuecomment-263524729](https://github.com/ethereum/EIPs/issues/20#issuecomment-263524729)). |

error[markdown-rel-links]: non-relative link or image --> ERCS/erc-1363.md | 198 | This proposal has been inspired also by [ERC-223](https://github.com/ethereum/EIPs/issues/223) and [ERC-677](https://github.com/ethereum/EIPs/issues/677) but it uses the [ERC-721](./eip-721.md) approach, so it doesn't override the [ERC-20](./eip-20.md) `transfer` and `transferFrom` methods and defines the interfaces IDs to be implemented maintaining the [ERC-20](./eip-20.md) backwards compatibility. | = help: see https://ethereum.github.io/eipw/markdown-rel-links/

error[markdown-rel-links]: non-relative link or image --> ERCS/erc-1363.md | 198 | This proposal has been inspired also by [ERC-223](https://github.com/ethereum/EIPs/issues/223) and [ERC-677](https://github.com/ethereum/EIPs/issues/677) but it uses the [ERC-721](./eip-721.md) approach, so it doesn't override the [ERC-20](./eip-20.md) `transfer` and `transferFrom` methods and defines the interfaces IDs to be implemented maintaining the [ERC-20](./eip-20.md) backwards compatibility. |

error[markdown-rel-links]: non-relative link or image --> ERCS/erc-1363.md | 205 | One possible solution to mitigate this race condition is to first reduce the spender's allowance to 0 and set the desired value afterwards ([EIP-20#issuecomment-263524729](https://github.com/ethereum/EIPs/issues/20#issuecomment-263524729)). |

error[preamble-re-discussions-to]: preamble header `discussions-to` should point to a thread on ethereum-magicians.org --> ERCS/erc-1363.md:5:16 | 5 | discussions-to: https://github.com/ethereum/eips/issues/1363 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ required pattern was not matched | = info: the pattern in question: `^https://ethereum-magicians.org/t/[^/]+/[0-9]+$` = help: see https://ethereum.github.io/eipw/preamble-re-discussions-to/

error[preamble-req]: preamble is missing header(s): `description` --> ERCS/erc-1363.md | | = help: see https://ethereum.github.io/eipw/preamble-req/

validation found errors :(