8000 Flag --watch does not watch for file changes · Issue #1045 · google/clasp · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Flag --watch does not watch for file changes #1045

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

Closed
yagodlt opened this issue Mar 24, 2025 · 5 comments
Closed

Flag --watch does not watch for file changes #1045

yagodlt opened this issue Mar 24, 2025 · 5 comments
Labels

Comments

@yagodlt
Copy link
yagodlt commented Mar 24, 2025

Just updated to clasp 3.0.2 alpha and the --watch flag is no longer working. This is a BIG deal for me.

Behaviour description when running clasp push --watch:

Expected behaviour: Clasp pushes files and then remains "Waiting for changes..."
Actual behaviour:

  • Clasp pushes the files if there have been any updates
  • Clasp shows "Waiting for changes..."
  • The scripts finishes and the user is back at the normal prompt. No changes are being watched

Attached is a copy of the debug info obtained after using DEBUG=clasp:* clasp push --watch. I have removed sensitive information and the code that was being pushed as it is irrelevant for this report.

I have also attached a screenshot of the clasp push --watch command when run without verbose debugging.

clasp.log

Image

@yagodlt
Copy link
Author
yagodlt commented Mar 24, 2025

The obvious workaround is to install a 2.x version for now.

@hgodinho
Copy link

same here

Pushed 2 files.
└─ src/appsscript.json
└─ src/Código.js
Waiting for changes...
/app/packages/mvp-0 # 

@sqrrrl
Copy link
Member
sqrrrl commented Mar 24, 2025

Ah, sorry, just broke this in last release. Will push a fix shortly.

@sqrrrl
Copy link
Member
sqrrrl commented Mar 25, 2025

Fixed in 3.0.3

@sqrrrl sqrrrl closed this as completed Mar 25, 2025
@sqrrrl
Copy link
Member
sqrrrl commented Mar 25, 2025

Err, at least fixed as far as I could reproduce, which looked like it was an issue when using rootDir. That dir was getting checked first and was ignored, causing it to short circuit and exit. 5DFD Found another bug with the ignore processing inside watch (paths needed to be made relative to project root) and fixed that too, so should be OK now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants
0