thanks for this Mikael really helped me out!
FYI i've actually started using clasp with a slightly simpler setup, avoiding the gulpfile, though probs more limited:
seems like you can get a long way with those server errors just by including an exports.js file containing:
exports.js
var exports = {};
then in my npm package.json scripts to turn client .js files into .js.html files:
package.json
... "scripts": { "test": "npm run build && mocha --exit --recursive --file test-stubs.js", "build": "for file in client/*.js; do cp \"$file\" \"$file.html\"; done" }, ...
also ATM i have stubs for the google server bits while i work out how best to test them, a .js file (included in .claspignore) containing for me:
var localFunctions = { loadQueries: function() {}, checkActivity: function() {} } var run = { withSuccessHandler: function() { return localFunctions } } global.google = { script: { run: run } };
which works... for now!
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
thanks for this Mikael really helped me out!
FYI i've actually started using clasp with a slightly simpler setup, avoiding the gulpfile, though probs more limited:
seems like you can get a long way with those server errors just by including an
exports.js
file containing:then in my npm
package.json
scripts to turn client .js files into .js.html files:also ATM i have stubs for the google server bits while i work out how best to test them, a .js file (included in .claspignore) containing for me:
which works... for now!