prompt: Your task is to convert an English description into an ASCII tree format using this style:
  ```
  fixtures
   +--behavior
   |   +--get-with-falsy-receiver
   |   `--get-without-receiver
   +--dependencies
   |   +--basic
   |   +--deep
   |   +--missing
   |   +--multiple
   |   +--rename-binding-equal
   |   +--rename-deep-global
   |   +--reuse-dependency
   |   `--variable-same-name-dependency
   `--misc
       +--9496
  ```
  
  Convert this description:
  
  fixtures is a top-level directory that maintains 4 subdirectories. Notable ones include flow-compat, jsx-compat, node-extensions among others.
  
  Let me break down the ordering for you:
  
  In the root directory, 'flow-compat' stores 6 a few folders.
  In nested path 'flow-compat > js-invalid', The 'js-invalid' storage space has no content.
  In nested path 'flow-compat → js-valid', The 'js-valid' directory is currently empty.
  Within directory hierarchy 'flow-compat > ts-invalid', Inside 'ts-invalid', you'll find it is an empty container.
  Within directory hierarchy 'flow-compat > ts-valid', The 'ts-valid' container stands empty.
  In nested path 'flow-compat → tsx-invalid', 'tsx-invalid' is empty.
  Within directory hierarchy 'flow-compat > tsx-valid', The 'tsx-valid' data structure lacks any subdirectories.
  At the main level, 'jsx-compat' encapsulates 4 various child directories.
  In nested path 'jsx-compat / js-valid', Inside 'js-valid', you'll find it contains nothing at present.
  Within directory hierarchy 'jsx-compat → ts-invalid', 'ts-invalid' contains no subdirectories.
  In nested path 'jsx-compat → ts-invalid-babel-7', The 'ts-invalid-babel-7' collection hasn't been filled with any content.
  Within directory hierarchy 'jsx-compat → tsx-valid', Inside 'tsx-valid', you'll find it appears to be unused.
  At the main level, 'node-extensions' carries 10 assorted nested folders.
  At level 2, in directory path 'node-extensions > import-in-cts', 'import-in-cts' is vacant.
  At level 2, in directory path 'node-extensions / import-in-mts', 'import-in-mts' has been left empty.
  Within directory hierarchy 'node-extensions → type-assertion-in-cts', 'type-assertion-in-cts' is barren.
  At level 2, in directory path 'node-extensions / type-assertion-in-mts', Inside 'type-assertion-in-mts', you'll find it holds no subdirectories at the moment.
  At level 2, in directory path 'node-extensions > type-assertion-in-ts', The 'type-assertion-in-ts' repository is currently empty.
  At level 2, in directory path 'node-extensions > type-param-arrow-in-cts', The 'type-param-arrow-in-cts' collection is devoid of content.
  In nested path 'node-extensions / type-param-arrow-in-mts', Inside 'type-param-arrow-in-mts', you'll find it awaits content.
  Within directory hierarchy 'node-extensions / type-param-arrow-in-ts', 'type-param-arrow-in-ts' is blank.
  At level 2, in directory path 'node-extensions > with-in-cts', Inside 'with-in-cts', you'll find it has been left empty.
  In nested path 'node-extensions → with-in-mts', Inside 'with-in-mts', you'll find it sits empty.
  In the root directory, 'opts' keeps 6 a few child directories.
  At level 2, in directory path 'opts > allExtensions-true-isTSX-true', The 'allExtensions-true-isTSX-true' data structure appears to be unused.
  At level 2, in directory path 'opts → allowDeclareFields', 'allowDeclareFields' lacks any subdirectories.
  At level 2, in directory path 'opts → ignoreExtensions', Inside 'ignoreExtensions', you'll find it appears to be unused.
  Within directory hierarchy 'opts > optimizeConstEnums', 'optimizeConstEnums' is unpopulated.
  At level 2, in directory path 'opts → rewriteImportExtensions', Inside 'rewriteImportExtensions', you'll find it awaits content.
  In nested path 'opts / rewriteImportExtensions-createImportExpressions', The 'rewriteImportExtensions-createImportExpressions' repository is blank.
  Back to the top level.
  
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "fixtures\n +--flow-compat\n |   +--js-invalid\n |   +--js-valid\n |   +--ts-invalid\n |   +--ts-valid\n |   +--tsx-invalid\n |   `--tsx-valid\n +--jsx-compat\n |   +--js-valid\n |   +--ts-invalid\n |   +--ts-invalid-babel-7\n |   `--tsx-valid\n +--node-extensions\n |   +--import-in-cts\n |   +--import-in-mts\n |   +--type-assertion-in-cts\n |   +--type-assertion-in-mts\n |   +--type-assertion-in-ts\n |   +--type-param-arrow-in-cts\n |   +--type-param-arrow-in-mts\n |   +--type-param-arrow-in-ts\n |   +--with-in-cts\n |   `--with-in-mts\n `--opts\n     +--allExtensions-true-isTSX-true\n     +--allowDeclareFields\n     +--ignoreExtensions\n     +--optimizeConstEnums\n     +--rewriteImportExtensions\n     `--rewriteImportExtensions-createImportExpressions", "description": "fixtures is a top-level directory that maintains 4 subdirectories. Notable ones include flow-compat, jsx-compat, node-extensions among others.\n\nLet me break down the ordering for you:\n\nIn the root directory, 'flow-compat' stores 6 a few folders.\nIn nested path 'flow-compat > js-invalid', The 'js-invalid' storage space has no content.\nIn nested path 'flow-compat \u2192 js-valid', The 'js-valid' directory is currently empty.\nWithin directory hierarchy 'flow-compat > ts-invalid', Inside 'ts-invalid', you'll find it is an empty container.\nWithin directory hierarchy 'flow-compat > ts-valid', The 'ts-valid' container stands empty.\nIn nested path 'flow-compat \u2192 tsx-invalid', 'tsx-invalid' is empty.\nWithin directory hierarchy 'flow-compat > tsx-valid', The 'tsx-valid' data structure lacks any subdirectories.\nAt the main level, 'jsx-compat' encapsulates 4 various child directories.\nIn nested path 'jsx-compat / js-valid', Inside 'js-valid', you'll find it contains nothing at present.\nWithin directory hierarchy 'jsx-compat \u2192 ts-invalid', 'ts-invalid' contains no subdirectories.\nIn nested path 'jsx-compat \u2192 ts-invalid-babel-7', The 'ts-invalid-babel-7' collection hasn't been filled with any content.\nWithin directory hierarchy 'jsx-compat \u2192 tsx-valid', Inside 'tsx-valid', you'll find it appears to be unused.\nAt the main level, 'node-extensions' carries 10 assorted nested folders.\nAt level 2, in directory path 'node-extensions > import-in-cts', 'import-in-cts' is vacant.\nAt level 2, in directory path 'node-extensions / import-in-mts', 'import-in-mts' has been left empty.\nWithin directory hierarchy 'node-extensions \u2192 type-assertion-in-cts', 'type-assertion-in-cts' is barren.\nAt level 2, in directory path 'node-extensions / type-assertion-in-mts', Inside 'type-assertion-in-mts', you'll find it holds no subdirectories at the moment.\nAt level 2, in directory path 'node-extensions > type-assertion-in-ts', The 'type-assertion-in-ts' repository is currently empty.\nAt level 2, in directory path 'node-extensions > type-param-arrow-in-cts', The 'type-param-arrow-in-cts' collection is devoid of content.\nIn nested path 'node-extensions / type-param-arrow-in-mts', Inside 'type-param-arrow-in-mts', you'll find it awaits content.\nWithin directory hierarchy 'node-extensions / type-param-arrow-in-ts', 'type-param-arrow-in-ts' is blank.\nAt level 2, in directory path 'node-extensions > with-in-cts', Inside 'with-in-cts', you'll find it has been left empty.\nIn nested path 'node-extensions \u2192 with-in-mts', Inside 'with-in-mts', you'll find it sits empty.\nIn the root directory, 'opts' keeps 6 a few child directories.\nAt level 2, in directory path 'opts > allExtensions-true-isTSX-true', The 'allExtensions-true-isTSX-true' data structure appears to be unused.\nAt level 2, in directory path 'opts \u2192 allowDeclareFields', 'allowDeclareFields' lacks any subdirectories.\nAt level 2, in directory path 'opts \u2192 ignoreExtensions', Inside 'ignoreExtensions', you'll find it appears to be unused.\nWithin directory hierarchy 'opts > optimizeConstEnums', 'optimizeConstEnums' is unpopulated.\nAt level 2, in directory path 'opts \u2192 rewriteImportExtensions', Inside 'rewriteImportExtensions', you'll find it awaits content.\nIn nested path 'opts / rewriteImportExtensions-createImportExpressions', The 'rewriteImportExtensions-createImportExpressions' repository is blank.\nBack to the top level.\n"}