-
-
Notifications
You must be signed in to change notification settings - Fork 390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chokidar is only available when dev dependencies are installed #1399
Comments
I see |
That sounds great - thanks for the quick reply! 😄 |
## Context I'm trying to add `grist-core` to nixpkgs and during testing it became clear that `chokidar` is only available as a dev dependency. ## Proposed solution Remove the import and use of `chokidar` as it's no longer used as per #1399 (comment) ## Related issues closes #1399 <!-- If suggesting a new feature or change, please discuss it in an issue first --> <!-- If fixing a bug, there should be an issue describing it with steps to reproduce --> <!-- If this does not solve entirely the issue, make also a checklist of what is done or not: --> ## Has this been tested? <!-- Put an `x` in the box that applies: --> - [ ] 👍 yes, I added tests to the test suite - [ ] 💭 no, because this PR is a draft and still needs work - [x] 🙅 no, because this is not relevant here - [ ] 🙋 no, because I need help <!-- Detail how we can help you --> ## Screenshots / Screencasts <!-- delete if not relevant --> Co-authored-by: Christian Ravn <[email protected]>
Describe the current behavior
When building
chokidar
is currently provided bychokidar-cli
, which is listed as a dev dependency. If only the regular dependencies are provided, then grist fails due to the missing module.Steps to reproduce
yarn build:prod
yarn --prod install
Describe the expected behavior
It should be possible to run grist without having to install the dev dependencies, since they add approximately 400MiB to the install size.
Where have you encountered this bug?
Instance information (when self-hosting only)
Grist instance:
Browser name, version and platforms on which you could reproduce the bug:
Link to browser console log if relevant:
Link to server log if relevant:
The text was updated successfully, but these errors were encountered: