You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I have my package.json in the same folder as mocks.config.js and collections.js, even if I configure the collections.json filepath properly in the mocks.config.js, it cannot be found.
To Reproduce
Have a package.json in the same folder as mocks.config.js and collections.js. Configure the collections.json filepath in the mocks.config.js as file.path: '.'
Expected behavior
Expected to work the same way as in a parent folder.
Logs
I don't have the setup at the moment.
** Operating system, Node.js an npm versions, or browser version (please complete the following information):**
OS: Mac
Node.js: 18
npm: 8
Browser: N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Hi @bcsikos-agi , I'm sorry but, for the moment the folder containing routes and collections can't be the project folder itself. Note that the server watches for changes in the files, and it cleans the require cache each time a file is modified, so, it may produce to clean the cache of the of the server itself, because the project root usually contains the node_modules folder containing it.
Maybe this could be achieved by allowing to provide a separated configuration for the collections file, or by providing an option for ignoring certain subpaths.
Describe the bug
When I have my package.json in the same folder as mocks.config.js and collections.js, even if I configure the collections.json filepath properly in the mocks.config.js, it cannot be found.
To Reproduce
Have a package.json in the same folder as mocks.config.js and collections.js. Configure the collections.json filepath in the mocks.config.js as file.path: '.'
Expected behavior
Expected to work the same way as in a parent folder.
Logs
I don't have the setup at the moment.
** Operating system, Node.js an npm versions, or browser version (please complete the following information):**
Additional context
N/A
The text was updated successfully, but these errors were encountered: