HaoYang670 opened a new issue, #262:
URL: https://github.com/apache/arrow-ballista/issues/262

   **Describe the bug**
   ```
   remziy@remziy-mlt:scheduler$ yarn start           
   yarn run v1.22.19
   $ react-scripts start
   node:internal/modules/cjs/loader:498
         throw e;
         ^
   
   Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/tokenize' is 
not defined by "exports" in 
/Users/remziy/FangcloudV2/personal_space.localized/working/Ballista/ballista/ui/scheduler/node_modules/postcss-safe-parser/node_modules/postcss/package.json
       at new NodeError (node:internal/errors:393:5)
       at throwExportsNotFound (node:internal/modules/esm/resolve:340:9)
       at packageExportsResolve (node:internal/modules/esm/resolve:619:3)
       at resolveExports (node:internal/modules/cjs/loader:492:36)
       at Module._findPath (node:internal/modules/cjs/loader:532:31)
       at Module._resolveFilename (node:internal/modules/cjs/loader:941:27)
       at Module._load (node:internal/modules/cjs/loader:803:27)
       at Module.require (node:internal/modules/cjs/loader:1021:19)
       at require (node:internal/modules/cjs/helpers:103:18)
       at Object.<anonymous> 
(/Users/remziy/FangcloudV2/personal_space.localized/working/Ballista/ballista/ui/scheduler/node_modules/postcss-safe-parser/lib/safe-parser.js:1:17)
 {
     code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
   ```
   
   Env:
   ```
   remziy@remziy-mlt:scheduler$ yarn --version
   1.22.19
   remziy@remziy-mlt:scheduler$ node --version
   v18.9.0
   ```
   
   It could run successfully after I removed `node_modules` and `yarn.lock`
   
   **To Reproduce**
   Steps to reproduce the behavior:
   
   **Expected behavior**
   It should run successfully.
   
   **Additional context**
   Add any other context about the problem here.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to