Inbox files as iterable

Actually, the way to read the inbox queue of file names is by manually looping over inbox.nextFile() until it returns nothing.

That's already solved with iterables.
Can you oevolve that API to expose something like this:

const inboxFiles = {
	next: () => {
		const value = inbox.nextFile();
		return {
			value: value as string,
			done: !value,
		};
	},
	[Symbol.iterator]: function () {
		return this;
	},
};

So we can do stuff like

for (const fileName of inboxFiles) {
	doStuff(fileName);
}

compared to:

let fileName = inbox.nextFile();
while (fileName) {
	doStuff(fileName);
	fileName = inbox.nextFile(fileName);
}

The dependency rollup was updated from 1.27.6 to 1.27.7.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency @types/lodash was updated from 4.14.140 to 4.14.141.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/lodash is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I am not sure if this is the right place to request this but I figured the build toolchain is a good start.

It would be really nice if the CSS in Fitbit OS apps could support some form of variables. Even if the CSS interpreter on the watch does not support it, I thought maybe it could be something that is compiled during the build process.

just a thought. thanks!

Hi, currently trying to run npx fitbit-build on Node 17 fails with an error because of the following:

Right now during development I need to do the following in order to view my changes

> npx fitbit-build
> npx fitbit
> fitbit$ install

and as you already know you can do both the build and in the install inside the fitbit$ shell

feature request

I would like there to be a fitbit-install just like there is a fitbit-build

why?

I would like to setup my own file watchers and have them automatically run both fitbit-build then fitbit-install. Right now there's no real way (that i know of yet) to do that.

The devDependency @types/lodash was updated from 4.14.120 to 4.14.121.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/lodash is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

1. Actually, we are transpiling and generating helpers with TypeScript.
2. Nowdays, the state of the art is to split linting, type checking, transpilation and bundling into different tools/steps. Here we are mixing type-checking and transpilation.
   1.1. This is important because the used JS engine, jerryscript, supports not just full ECMAScript 5.1, but also some interesting features of ES2015 (you can se them listed in the release notes).

By using Babel to transform the code, we can customize which transformations we want, and skip the ones that JerryScript 2.1 already handles natively.

JerryScript support of ES2015 features

Use Babel + JerryScript following https://github.com/jerryscript-project/jerryscript/tree/v2.1.0/tools/babel

Ran the CLI for the first time today and created a new project however when I try to run a build I fail to get a build folder. The CLI says it completes the build but no build folder is contained within the project and I can't find any builds located anywhere else on my machine. Any idea why this is happening and how to fix it?

The dependency rollup was updated from 1.15.6 to 1.16.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency prettier was updated from 1.18.2 to 1.19.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I've upgraded my clockface project with SDK types (converted to Typescript). Now during build I am getting this error:

> [email protected] build /Users/ygalanter/Documents/Github Personal/Clean-Smart-Plus/clockfaces/pre-atlas
> fitbit-build

[09:43:05][error][app] TypeError: Cannot read property 'text' of undefined
    Details:
        code: PLUGIN_ERROR
        hook: transform
        id: /Users/ygalanter/Documents/Github Personal/Clean-Smart-Plus/clockfaces/pre-atlas/app/index.ts
        watchFiles: /Users/ygalanter/Documents/Github Personal/Clean-Smart-Plus/clockfaces/pre-atlas/app/index.ts

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build: `fitbit-build`
npm ERR! Exit status 1

It doesn't point to any line in my code and AFAIK all every element that uses .text property is defined.
clockface_project.zip

I'm running on a cloud server that doesn't have a machine ID in /etc/machine-id, and I cannot create one due to permission issues.
When running npx fitbit, I get the following error:

Failed to read auth token from keychain: Error: Cannot spawn a message bus without a machine-id: Invalid machine ID in /nix/store/f5jhxrj5cxq2mnahwj4nba3sw4g5956c-glib-2.70.1/var/lib/dbus/machine-id or /etc/machine-id

I also can't make one in /nix/store/f5jhxrj5cxq2mnahwj4nba3sw4g5956c-glib-2.70.1/var/lib/dbus/machine-id , by the way.

Any way to do this without a valid machine ID?

The devDependency @types/jest was updated from 24.0.9 to 24.0.10.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Many watch faces are broken in Versa 2 because <gradientRect> is not displayed on the device. The simulator works fine.

I guess this is hardly a problem of the SDK toolchain, but this repo is the closest thing to a public bug tracker for issues of that sort and this one is a high severity issue.

This snap is for cover pic, for the same issue on Profile Pic, I had to manually upload it by hitting the post service of it.

The dependency rollup was updated from 1.4.2 to 1.5.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Hi, I noticed my new Inspire HR has an "apps" tab and I was wondering if it's possible to develop apps for it? I looked at this SDK but I'm not sure if the same OS is used on the Inspires?

The devDependency prettier was updated from 1.17.1 to 1.18.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I've been looking over things, and not finding this anywhere. Versa 2 (Mira) supports BT. I can play audio over it using built-ins. I'm not find that functionality anywhere in the API, and would like to see it to develop a custom music player that doesn't rely on a phone being nearby or network access.

The dependency io-ts was updated from 1.5.2 to 1.5.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

io-ts is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency rollup was updated from 1.14.2 to 1.14.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

There have been updates to the babel7 monorepo:

• • The dependency @babel/core was updated from 7.7.7 to 7.8.0.

• The dependency @babel/plugin-syntax-dynamic-import was updated from 7.8.0 to 7.8.3.
• The dependency @babel/plugin-transform-block-scoped-functions was updated from 7.8.0 to 7.8.3.
• The dependency @babel/plugin-transform-block-scoping was updated from 7.8.0 to 7.8.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency rollup was updated from 1.20.1 to 1.20.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

The devDependency @types/yargs was updated from 12.0.2 to 12.0.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/yargs is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency update-notifier was updated from 2.5.0 to 2.6.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

update-notifier is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency yargs was updated from 13.2.2 to 13.2.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

yargs is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency lint-staged was updated from 8.1.0 to 8.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

lint-staged is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

This seems like a tiny issue, but I thought I'd report it. When both Versa and Ionic emulators are set to certain battery levels, they report a different battery level to the emulator.

Setting level 29 reports 28. (See screen shot. )
Setting level 57 reports 56.
Setting level 58 reports 57.

I have verified all other battery values are correct.
In my code I am using these lines to derive the battery level:

var batlvl = Math.floor(battery.chargeLevel);
powerRow.text = batlvl;

So it could be some kind of round-off error. I also attempted to remove the Math.floor() function but received the same results. Again, not a critical issue, but something that should be documented. Thanks!