Closed aparnak799 closed 9 months ago
Usually you don't need to have to run npm update
John Alexis Guerra Gómez On my phone, brevity and all
On Sun, Sep 17, 2023, 4:47 PM Aparna Krishnan @.***> wrote:
When attempting to execute the custom npm run dev script, I encounter a TypeError related to redefining a property named File. The error traces back to the @babel/core module. I have not made any direct modifications to this module, and the issue presents itself specifically during the execution of the aforementioned script.
Running npm update first used to solve this issue in a previous version of this repository, but it no longer does.
Error message:
[!] TypeError: Cannot redefine property: File at Function.defineProperty (
) at Object. @.\core\lib\index.js:7:8) at Module._compile (node:internal/modules/cjs/loader:1241:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1295:10) at Module.load (node:internal/modules/cjs/loader:1091:32) at Function.Module._load (node:internal/modules/cjs/loader:938:12) at Module.require (node:internal/modules/cjs/loader:1115:19) at require (node:internal/modules/helpers:130:18) at Object. @.\core\src\config\helpers\config-api.ts:4:1) at Module._compile (node:internal/modules/cjs/loader:1241:14) Steps to reproduce:
- Clone the repository to local machine
- Run npm install and npm update from within repository
- Run npm run dev
— Reply to this email directly, view it on GitHub https://github.com/ivelascog/TimeSearcherPlus/issues/3, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJJCSYGOE7S5XARPOFFRMDX26DZJANCNFSM6AAAAAA4354D7I . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Yes, but running npm update was cited online as one of the possible fixes to resolve issues with babel files It doesn't work now anyway, so I think we need to find other ways of resolving this issue.
When attempting to execute the custom npm run dev script, I encounter a TypeError related to redefining a property named File. The error traces back to the @babel/core module. I have not made any direct modifications to this module, and the issue presents itself specifically during the execution of the aforementioned script.
Running npm update first used to solve this issue in a previous version of this repository, but it no longer does.
Error message:
Steps to reproduce: