-
Notifications
You must be signed in to change notification settings - Fork 419
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
Clarify what exactly the fileExtension
setting in clasp.json does
#1001
Comments
fileExtension is used more for pulling from the apps script to local, but doesn't affect filtering when pushing. Two recommendations for avoiding pushing node_modules:
Personally I used the latter approach and point to a ./dist or ./build dir that contains the output of any build steps. That way you can use rollup or other tools to leverage modules, import npm packages, etc. and have it output code that is flattened and compatible with apps script as a runtime. See https://github.com/sqrrrl/apps-script-typescript-rollup-starter as an example (though realized I didn't check in the template clasp configs) |
Thanks! Would be great to add that explanation of |
Expected Behavior
My
clasp.json
looks like this:Actual Behavior
clasp push
pushes all.ts
and.js
files, even from./node_modules
. I expected it to only push.gs
files. Combined with #983, this seriously hinders usability.The README section for
fileExtension
says,What exactly does that mean?
Furthermore, the documentation for Push states it ignores files "That don't have an accepted file extension". Where is that accepted file extension configured?
Specifications
node -v
): v18.19.0clasp -v
): 2.4.2 (latest, released Sep 2022)The text was updated successfully, but these errors were encountered: