
Security News
TC39 Advances Temporal to Stage 4 Alongside Several ECMAScript Proposals
TC39’s March 2026 meeting advanced eight ECMAScript proposals, including Temporal reaching Stage 4 and securing its place in the ECMAScript 2026 specification.
ember-cli-mobile-chrome-apps
Advanced tools
This Ember Addon provides commands to build your project as a chrome or cordova app, using Google's MobileChromeApps
Install the addon by running:
npm install ember-cli-mobile-chrome-apps
Run ember help for a detailed list of all commands and arguments.
First generate the chrome app by running:
ember g chrome
This commands generates a folder apps in the root of your project.
Both the chrome and cordova apps will appear in it.
In apps/chrome you'll find background.js and a default manifest.json that you can change according to your needs. For more information about the manifest see this link.
You can add files and folders from your dist to the chrome app by copying or symlinking them in the apps/chrome directory.
window.html and the assets folder have already been added as a default.
This way you can manage which parts of your Ember CLI app will be added to your chrome app.
ember chrome:build
This command builds the chrome app from the apps/chrome folder.
It will generate a project_name.zip and a signed project_name.crx file in apps/chrome/dist.
You can specify the location of the key in the config/mobile-chrome-apps.js file.
The command will also build your ember cli project (you can skip this using --skip-build or change the build environment using --environment).During development you don't have to build your project all the time, you can just go to chrome://extensions with chrome and click 'Load unpacked extension'. Then choose the apps/chrome folder and you'll see the app appear in chrome.
If you have a working chrome app you can add cordova by running:
ember g cordova
This will generate a manifest.mobile.json file in apps/chrome that contains your app's packageId (for example com.example.ProjectName). You can update this to your desired packageId.
It will also generate the apps/cordova folder that contains the cordova project.
ember cordova:checkenv
Before being able to use cordova properly you should run this command to verify that you have set up your working environments for Android and iOS correctly.ember cordova:build
With this command you can build your cordova project and optionally --release it.ember cordova:run
The run command can be used to emulate the app or deploy it to a developer device.
For example ember cordova:run --android --emulate will emulate your android app.
ember cordova:run --ios --device will deploy the app to an iOS developer device.ember cordova:upgrade
This command can be used to upgrade your cordova project when a new version of google's cca is being released.
You'll also be prompted to do so when you build the app and there is an update.locationType is set to hash in your config/environment.js file.apps/chrome/window.html to dist/index.html, the asset urls in app/index.html will be compiled like normal. However, if you have a different window.html, it will not be compiled and thus will not be able to handle fingerprinted assets. In that case you have to disable it in ember-cli-build.js by setting fingerprint to { enabled: false }.This project is released under the MIT License.
FAQs
Build your Ember CLI project as a chrome or cordova app
The npm package ember-cli-mobile-chrome-apps receives a total of 0 weekly downloads. As such, ember-cli-mobile-chrome-apps popularity was classified as not popular.
We found that ember-cli-mobile-chrome-apps demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
TC39’s March 2026 meeting advanced eight ECMAScript proposals, including Temporal reaching Stage 4 and securing its place in the ECMAScript 2026 specification.

Research
/Security News
Since January 31, 2026, we identified at least 72 additional malicious Open VSX extensions, including transitive GlassWorm loader extensions targeting developers.

Research
Six malicious Packagist packages posing as OphimCMS themes contain trojanized jQuery that exfiltrates URLs, injects ads, and loads FUNNULL-linked redirects.