GithubHelp home page GithubHelp logo

mike-north / ember-intercom-io Goto Github PK

View Code? Open in Web Editor NEW
52.0 5.0 30.0 3.57 MB

Deep intercom.io integration for Ember.js apps

License: MIT License

JavaScript 93.20% HTML 5.37% CSS 0.19% Handlebars 1.25%
intercom ember-apps addon chat

ember-intercom-io's Introduction

ember-intercom-io

Build Status Code Climate Dependency Status devDependency Status Ember Observer Score

Intercom.io integration for Ember.js apps.

Setup

Install this addon with ember-cli ember install ember-intercom-io

Add the {{intercom-io}} component to one of your templates` The chat widget will appear whenever this component has been rendered, and should disappear whenever it's destroyed.

Configuration

In your config/environment.js file, you must provide your appId

module.exports = function(environment) {
  ...
  intercom: {
    appId: null, // <-- REPLACE WITH YOUR INTERCOM.IO app_id
    enabled: true, // <-- Setting to false in your testing environment prevents unneccessary network requests (true by default)
    userProperties: {
      createdAtProp: 'createdAt',
      emailProp: 'email',
      nameProp: 'name',
      userHashProp: 'hash',
      userIdProp: 'id'
    }
  },
  ...
};

Users vs Leads

In the intercom.io world, a lead is a visitor to your site or app, without an email or name associated with them. A user has a name and email, and is a good construct for tracking the history of all interactions w/ a single person.

You can make ember-intercom-io aware of a "user" context (shifting into "users" mode instead of "leads" mode) by adding an object to the intercom service (i.e., your user authentication service).

When the application updates the intercom.user object, changes will be sent to Intercom and reflected in your Intercom dashboard.

app/services/authentication.js

import Service, {inject as service} from '@ember/service';

export default Service.extend({
  intercom: service(), // the intercom service
  didLogin(user) {
    ...
    this.get('intercom').set('user.name', 'Joe Username');
    this.get('intercom').set('user.email', '[email protected]');
    this.get('intercom').set('user.createdAt', 1447135065173);
  }
});

Custom Properties

To send custom properties on to intercom, add them to the intercom.user object. All property names will be underscored prior to being sent. undefined values will be removed (however, null is kept).

  let customProperties = {
    myCustomThing: 1,
    numberOfCats: false,
    notDefined: undefined
  }
  set(this, 'intercom.user', customProperties);

becomes

{
  my_custom_thing: 1,
  number_of_cats: false
}

API

The intercom service exposes several public API methods that match Intercom.com's existing Javascript API. For full details on the client API, read the Intercom docs.

Properties

Name Type
autoUpdate Boolean
hideDefaultLauncher Boolean
isOpen Boolean
isBooted Boolean
unreadCount Integer
user Object

Methods

The following intercom methods are implemented. See services/intercom.js for full details.

boot()

update()

shutdown()

hide()

show()

showMessages()

showNewMessage()

trackEvent()

getVisitorId() Returns the current id of the logged in user.

startTour() Your intercom account needs to support product tours

Events

Subscribe to events in your app with event listeners:

//fancy-component.js

...

intercom: service(),
newMessageAlert: on('intercom.unreadCountChange', function() {
    alert('Unread Count Changed!');
}),

...

Available Events

(Read the Intercom documentation for full details)[https://developers.intercom.com/v2.0/docs/intercom-javascript#section-intercomonhide]

Ember Event Intercom Event
hide onHide
show onShow
unreadCountChange onUnreadCountChange

Installation

  • git clone this repository
  • npm install

Linting

  • npm run lint:hbs
  • npm run lint:js
  • npm run lint:js -- --fix

Running tests

  • ember test – Runs the test suite on the current Ember version
  • ember test --server – Runs the test suite in "watch mode"
  • ember try:each – Runs the test suite against multiple Ember versions

Running the dummy application

For more information on using ember-cli, visit http://www.ember-cli.com/.

Copyright (c) 2015 Levanto Financial, 2016-18 Mike Works, Inc.

ember-intercom-io's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

ember-intercom-io's Issues

Messenger launcher not displaying after updating Intercom App ID

Hi,

We recently switched app IDs with Intercom (account merge) and updated our apps, but the one app that is using ember-intercom-io stopped showing the launcher. We're using the latest version of ember-intercom-io.

There's a setting in Intercom to always show the launcher for users and visitors, which we have enabled. The intercom client itself has an option hideDefaultLauncher which defaults to false. Our other apps had an issue where we had to set hideDefaultLauncher to false explicitly, and we think it's because Intercom changed the default.

In ember-intercom-io, however, you can't set it to false. It looks like it doesn't really default to false, it defaults to just not overriding it. See here:

if (hideDefaultLauncher) {
obj.hideDefaultLauncher = true;
}

I forked this library and Yarn add'd it in development mode to try and fix that, but unfortunately the Intercom launcher still doesn't display.

Is there anything I might be missing or didn't think of? I also reached out to Intercom, we'll see if they respond.

Thanks in advance!

An in-range update of @types/ember is breaking the build 🚨

Version 2.8.6 of @types/ember was just published.

Branch Build failing 🚨
Dependency @types/ember
Current Version 2.8.5
Type devDependency

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

@types/ember 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.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

These problems occurred while renovating this repository. View logs.

  • WARN: Using npm packages for Renovate presets is now deprecated. Please migrate to repository-based presets instead.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

  • chore(deps): commitlint monorepo (patch) (@commitlint/cli, @commitlint/travis-cli)
  • chore(deps): ember-cli-dependency-checker
  • chore(deps): husky
  • chore(deps): @ember/optional-features
  • chore(deps): @mike-north/js-lib-renovate-config
  • chore(deps): ember-source
  • chore(deps): ember-try
  • chore(deps): husky
  • chore(deps): ember-try
  • chore(deps): husky
  • chore(deps): stable ember infrastructure (major) (ember-cli, ember-cli-babel, ember-cli-fastboot, ember-qunit, ember-resolver, ember-source, eslint-plugin-ember, qunit-dom)
  • chore: lockfile maintenance
  • 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

Detected dependencies

npm
package.json
  • @babel/plugin-proposal-object-rest-spread ^7.2.0
  • ember-cli-babel ^7.1.3
  • ember-cli-htmlbars ^6.0.0
  • @commitlint/cli 7.6.0
  • @commitlint/config-conventional 7.6.0
  • @commitlint/travis-cli 7.6.0
  • @ember/optional-features 1.0.0
  • @mike-north/js-lib-renovate-config 1.1.5
  • @mike-north/js-lib-semantic-release-config 1.0.1
  • @types/ember 3.1.2
  • @types/ember-qunit 3.4.10
  • @types/ember__test-helpers 0.7.12
  • broccoli-asset-rev 3.0.0
  • ember-cli 3.28.6
  • ember-cli-dependency-checker 3.3.1
  • ember-cli-eslint 5.1.0
  • ember-cli-fastboot 2.2.3
  • ember-cli-htmlbars-inline-precompile 3.0.2
  • ember-cli-inject-live-reload 2.1.0
  • ember-cli-release 1.0.0-beta.2
  • ember-cli-template-lint 1.0.0-beta.3
  • ember-cli-uglify 3.0.0
  • ember-disable-prototype-extensions 1.1.3
  • ember-export-application-global 2.0.1
  • ember-load-initializers 2.1.2
  • ember-maybe-import-regenerator 0.1.6
  • ember-qunit 5.1.5
  • ember-resolver 8.1.0
  • ember-sinon 4.1.1
  • ember-sinon-qunit 4.0.1
  • ember-source 4.11.0
  • ember-source-channel-url 1.2.0
  • ember-try 1.2.1
  • eslint-plugin-ember 10.6.1
  • eslint-plugin-node 11.1.0
  • husky 3.0.7
  • loader.js 4.7.0
  • qunit-dom 2.0.0
  • semantic-release 15.12.5
  • node 6.* || 8.* || >= 10.*
travis
.travis.yml
  • node 8
  • node 10

  • Check this box to trigger a request for Renovate to run again on this repository

An in-range update of eslint-plugin-ember is breaking the build 🚨

Version 5.1.1 of eslint-plugin-ember was just published.

Branch Build failing 🚨
Dependency eslint-plugin-ember
Current Version 5.1.0
Type devDependency

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

eslint-plugin-ember 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.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes v5.1.1

🐛 Bug Fix

  • #229 Fix no-capital-letters-in-routes so it deals with MemberExpressions. (@nlfurniss)

📝 Documentation

🏠 Internal

Committers: 4

Commits

The new version differs by 10 commits.

  • 73d8de7 5.1.1
  • a116354 Update CHANGELOG for v5.1.1.
  • d4ad322 Merge pull request #254 from rwjblue/drop-require-folder-tree
  • 9fb242f Drop require-folder-tree dependency.
  • 6c2202d Merge pull request #229 from nlfurniss/master
  • d156d27 Merge pull request #242 from Turbo87/update-jest
  • 610d39d tests/utils/ember-test: Convert described assertions into separate tests
  • 129ef62 Update jest to v21.2.1
  • 4138013 Closes #240 (#241)
  • 62a4a04 Fix no-capital-letters-in-routes so it deals with MemberExpressions

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Is there a versionning mistake ?

The last Release on NPM is 1.0.1
The last tag is 1.1.2
And the package.json version is 0.0.0 ...

Is it possible de clarify this point and publish an up-to-date version ? NPM + Release + package.json ?

Update of user requiring name to be set

_hasUserContext checks for _userNameProp to be set. Warning message in update() method indicates that only a userId / email needs to be set. Is this intentional? Message is contradicting the conditional.

E.g. I have an anonymous user, who then logs in and becomes identified so to say. Not all of my user do have a name set but all of them have an id or email. Setting the name to the email as a fallback / workaround doesn't feel right though.

Could the _hasUserContext check be changed to reflect the warning message or will this have any side-effects?

Extend user properties

Hi, I wonder if there is a way to extend user properties without extending your service?

Release new version with getWithDefault fix

Hi @mike-north thanks for your hard work on this!

Actually I'm tracking down all of my app dependencies with warning alerts looking for a way to contribute with this kind of change.

I came here because 1.2.1 of ember-intercom-io are raising an getWithDefault warning and I see that already fixed in master by #354, so can you please release a new version with this change?

Thanks again!

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot 📦🚀

An in-range update of ember-cli-babel is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 6.12.0 of ember-cli-babel was just published.

Branch Build failing 🚨
Dependency ember-cli-babel
Current Version 6.11.0
Type dependency

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

ember-cli-babel 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.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 6 commits.

  • d8f266c release v6.12.0 🎉
  • fd6c9a6 Merge pull request #204 from kellyselden/_shouldDoNothing
  • ea3a2c5 add test
  • 5442a39 add a no-op optimization
  • 4b68bef Merge pull request #199 from astronomersiva/remove_redundant_check
  • 1e1bba9 Remove redundant check for targets

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of ember-cli-dependency-checker is breaking the build 🚨

Version 2.2.0 of ember-cli-dependency-checker was just published.

Branch Build failing 🚨
Dependency ember-cli-dependency-checker
Current Version 2.1.1
Type devDependency

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

ember-cli-dependency-checker 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.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Disable widget loading on pages that don't use component

Is there a way to avoid making the requests to https://widget.intercom.io/widget/ in the pages that I'm not using the add-on?

In my case, I only use intercom for my users that are logged in, so If someone goes to my landing page without being logged in, I do not show the intercom widget.

I can easily control this by choosing on which route I should place the component {{intercom-io}}. But, even though the widget is not showing, I can still see the requests in the network tab, which represents around 250Kb of JS (gzipped).

It would be great if I could reduce this size, and only make the requests for the pages that actually need it.

Thanks in advance!

Action required: Greenkeeper could not be activated 🚨

🚨 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 we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

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

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

[QUESTION]: What is userHashProp?

Hi @mike-north,

This is just a question. I haven't been able to find what is userHashProp in Intercom. The default value is hash, but looking at the Intercom docs I only can find an attribute called: user_hash (https://developers.intercom.com/installing-intercom/docs/javascript-api-attributes-objects#section-data-attributes).

When a look at the request send to Intercom, that value seems to be ignored. Is it a mistake or I am missing something?

Best regards,
Daniel.

Initializer not creating Intercom script on page load

Hi there,

This looks like an awesome addon but I'm having an issue in getting to to work.

The ember-intercom initializer kicks in during app boot and the function to insert the intercom script tag is defined and attached to the window load event however it never triggers.

I've copied and pasted the code snippet that does this into my app.js file where it works beautifully, and included as snippet below.

Is it possible that the load event is being fired before the initializer is run?

  var w = window;
  var d = document;
  var i = function() {
    i.c(arguments)
  };
  i.q = [];
  i.c = function(args) {
    i.q.push(args)
  };
  w.Intercom = i;

  function l() {
    var s = d.createElement('script');
    s.type = 'text/javascript';
    s.async = true;
    s.src = `https://widget.intercom.io/widget/${Ember.get(config, 'intercom.appId')}`;
    var x = d.getElementsByTagName('script')[0];
    x.parentNode.insertBefore(s, x);
  }
  if (w.attachEvent) {
    w.attachEvent('onload', l);
  } else {
    w.addEventListener('load', l, false);
  }

An in-range update of ember-source is breaking the build 🚨

Version 2.18.1 of ember-source was just published.

Branch Build failing 🚨
Dependency ember-source
Current Version 2.18.0
Type devDependency

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

ember-source 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.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 12 commits.

  • 78717c5 Release v2.18.1.
  • 905dd01 Add v2.18.1 to CHANGELOG.md.
  • 8639d6a [BUGFIX lts] Enable some recovery of errors thrown during render.
  • 8d6600b [BUGFIX lts] Avoid excessively calling Glimmer AST transforms.
  • 6e0b9fd Add v2.17.1 to CHANGELOG.md
  • dcfb297 Add v2.16.2 to CHANGELOG.md.
  • 1f05c15 Ensure build-metadata.json is included in packed tarball.
  • c2b7d49 Publish metadata file to S3.
  • 2dc45b2 Merge pull request #16068 from rwjblue/update-backburner-release
  • 0e049fb [BUGFIX release] Update to [email protected].
  • dee84b0 Fix incorrect .travis.yml config for release branch.
  • ca01684 Begin publishing npm tarballs to S3.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Problem figuring out when to call `update()`

I have the following usage pattern:

  • When the user is on my login page, I do not have {{intercom-io}} loaded in my template
  • When the user logs in, session data is set into the intercom.user object
  • A page is loaded that does have the {{intercom-io}} helper loaded

The problem is that intercom.isBooted is not true when I go and set the user data as the template hasn't loaded {{intercom-io}} yet.

If I refresh the page, everything looks right, my current user is displayed when I click on the messenger and get the "Hi <username> 👋 " message instead of "Hi there 👋"

Can anyone suggest where the best place, in my Ember app, I could place an intercom.update() call so that my messenger is loaded with the current user data?

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

An in-range update of greenkeeper-lockfile is breaking the build 🚨

Version 1.13.0 of greenkeeper-lockfile was just published.

Branch Build failing 🚨
Dependency greenkeeper-lockfile
Current Version 1.12.0
Type devDependency

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

greenkeeper-lockfile 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.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v1.13.0

1.13.0 (2018-01-19)

Features

  • add basic Codeship CI Integration (258e9c0)
Commits

The new version differs by 3 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Additional user config

I've attempted to add additional user config details to pass to intercom by setting additional params in the service and initializing them in our config. When I console.log the intercom services user values, these values appear to be set, but none seem to be passed to Intercom.

I saw that PR #30 was supposed to add this ability, but it was not added to the docs, and it doesn't seem immediately clear to me how we are supposed to add custom attributes. Please could someone advise how we can do this, preferably with a short example?

Thank you!

Tracking events

I am trying to make the event tracking work.

I am doing it like this right now:

get(this, 'intercom.api')('trackEvent', 'created-spot');

My idea was to get the intercom from the api property of the addon.

And it works like that, but only in my application.js (I know because you can see it in the network).

If I put the line get(this, 'intercom.api')('trackEvent', 'created-spot'); in an action and toggle it with a button click, it doesn't work. I get no network or log at all.

Any ideas?

An in-range update of ember-cli-qunit is breaking the build 🚨

Version 4.3.0 of ember-cli-qunit was just published.

Branch Build failing 🚨
Dependency ember-cli-qunit
Current Version 4.2.1
Type devDependency

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

ember-cli-qunit 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.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 5 commits.

  • 8bc7d15 v4.3.0
  • 4f7d32e Add v4.3.0 to CHANGELOG.md.
  • 371b9fa Update minimum version of ember-qunit to 3.3.0.
  • f9da916 Update packages to latest allowed versions.
  • 4d418f4 Update yarn.lock to match package.json.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Production build fails with Babel error when version 1.1.5 is included

Hey! I have a situation with travis-web and ember-intercom-io 1.1.5 where ember build -prod fails with a Babel error:

Build Error (broccoli-persistent-filter:Babel > [Babel: ember-intercom-io]) in ember-intercom-io/components/intercom-io.js

Unknown option: .babel. Check out https://babeljs.io/docs/en/babel-core/#options for more information about options.

This is with Ember CLI 3.5.0 and Ember 3.6.0, though I had the same problem last week on Ember 3.5.1.

The build failure produces a verbose log which I’ve included here but I don’t know that it’s useful:

Stack Trace and Error Report
=================================================================================

ENV Summary:

TIME: Tue Dec 11 2018 10:37:48 GMT-0600 (Central Standard Time)
TITLE: ember
ARGV:

  • /usr/local/Cellar/nvm/0.33.11/versions/node/v10.7.0/bin/node
  • /usr/local/opt/nvm/versions/node/v10.7.0/bin/ember
  • build
  • -prod
    EXEC_PATH: /usr/local/Cellar/nvm/0.33.11/versions/node/v10.7.0/bin/node
    TMPDIR: /var/folders/33/f95011rs65z83zr5sqncbtsm0000gs/T
    SHELL: /bin/zsh
    PATH:
  • /usr/local/opt/nvm/versions/node/v10.7.0/bin
  • /usr/local/heroku/bin
  • /Users/b/.yarn/bin
  • /Users/b/.rbenv/bin
  • /usr/local/opt/rbenv/shims
  • /Applications/Postgres.app/Contents/Versions/9.3/bin
  • /usr/local/share/npm/bin
  • /usr/local/bin
  • /usr/bin
  • /bin
  • /usr/sbin
  • /sbin
  • /usr/local/bin
  • /usr/X11/bin
  • /Users/b/.cabal/bin
  • /Users/b/bin
  • /usr/local/opt/rbenv/shims
  • /usr/local/opt/rbenv/bin
  • /usr/local/bin
  • /usr/bin
  • /bin
  • /usr/sbin
  • /sbin
  • /usr/local/MacGPG2/bin
  • /opt/X11/bin
  • /Applications/Postgres.app/Contents/Versions/latest/bin
  • /Users/b/Documents/Travis/trvs/bin
    PLATFORM: darwin x64
    FREEMEM: 955793408
    TOTALMEM: 17179869184
    UPTIME: 1442599
    LOADAVG: 18.0166015625,11.31201171875,6.93359375
    CPUS:
  • Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz - 3500
  • Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz - 3500
  • Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz - 3500
  • Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz - 3500
    ENDIANNESS: LE
    VERSIONS:
  • ares: 1.14.0
  • cldr: 33.1
  • http_parser: 2.8.0
  • icu: 62.1
  • modules: 64
  • napi: 3
  • nghttp2: 1.32.0
  • node: 10.7.0
  • openssl: 1.1.0h
  • tz: 2018e
  • unicode: 11.0
  • uv: 1.22.0
  • v8: 6.7.288.49-node.15
  • zlib: 1.2.11

ERROR Summary:

  • broccoliBuilderErrorStack: ReferenceError: Unknown option: .babel. Check out https://babeljs.io/docs/en/babel-core/#options for more information about options.
    at throwUnknownError (/Users/b/Documents/Travis/t4/node_modules/@babel/core/lib/config/validation/options.js:123:11)
    at Object.keys.forEach.key (/Users/b/Documents/Travis/t4/node_modules/@babel/core/lib/config/validation/options.js:107:5)
    at Array.forEach ()
    at validateNested (/Users/b/Documents/Travis/t4/node_modules/@babel/core/lib/config/validation/options.js:83:21)
    at validate (/Users/b/Documents/Travis/t4/node_modules/@babel/core/lib/config/validation/options.js:74:10)
    at loadPrivatePartialConfig (/Users/b/Documents/Travis/t4/node_modules/@babel/core/lib/config/partial.js:66:50)
    at loadFullConfig (/Users/b/Documents/Travis/t4/node_modules/@babel/core/lib/config/full.js:43:39)
    at transformSync (/Users/b/Documents/Travis/t4/node_modules/@babel/core/lib/transform.js:41:38)
    at Object.transform (/Users/b/Documents/Travis/t4/node_modules/@babel/core/lib/transform.js:22:38)
    at resolve (/Users/b/Documents/Travis/t4/node_modules/@ember/test-helpers/node_modules/broccoli-babel-transpiler/lib/worker.js:11:29)
  • codeFrame: Unknown option: .babel. Check out https://babeljs.io/docs/en/babel-core/#options for more information about options.
  • errorMessage: ember-intercom-io/components/intercom-io.js: Unknown option: .babel. Check out https://babeljs.io/docs/en/babel-core/#options for more information about options.
    in /var/folders/33/f95011rs65z83zr5sqncbtsm0000gs/T/broccoli-66169P6wW2WhUEKHB/out-265-funnel_funnel_addon_js
    at broccoli-persistent-filter:Babel > [Babel: ember-intercom-io] (Babel: ember-intercom-io)
  • errorType: Build Error
  • location:
    • column: [undefined]
    • file: ember-intercom-io/components/intercom-io.js
    • line: [undefined]
    • treeDir: /var/folders/33/f95011rs65z83zr5sqncbtsm0000gs/T/broccoli-66169P6wW2WhUEKHB/out-265-funnel_funnel_addon_js
  • message: ember-intercom-io/components/intercom-io.js: Unknown option: .babel. Check out https://babeljs.io/docs/en/babel-core/#options for more information about options.
    in /var/folders/33/f95011rs65z83zr5sqncbtsm0000gs/T/broccoli-66169P6wW2WhUEKHB/out-265-funnel_funnel_addon_js
    at broccoli-persistent-filter:Babel > [Babel: ember-intercom-io] (Babel: ember-intercom-io)
  • name: BuildError
  • nodeAnnotation: Babel: ember-intercom-io
  • nodeName: broccoli-persistent-filter:Babel > [Babel: ember-intercom-io]
  • originalErrorMessage: Unknown option: .babel. Check out https://babeljs.io/docs/en/babel-core/#options for more information about options.
  • stack: ReferenceError: Unknown option: .babel. Check out https://babeljs.io/docs/en/babel-core/#options for more information about options.
    at throwUnknownError (/Users/b/Documents/Travis/t4/node_modules/@babel/core/lib/config/validation/options.js:123:11)
    at Object.keys.forEach.key (/Users/b/Documents/Travis/t4/node_modules/@babel/core/lib/config/validation/options.js:107:5)
    at Array.forEach ()
    at validateNested (/Users/b/Documents/Travis/t4/node_modules/@babel/core/lib/config/validation/options.js:83:21)
    at validate (/Users/b/Documents/Travis/t4/node_modules/@babel/core/lib/config/validation/options.js:74:10)
    at loadPrivatePartialConfig (/Users/b/Documents/Travis/t4/node_modules/@babel/core/lib/config/partial.js:66:50)
    at loadFullConfig (/Users/b/Documents/Travis/t4/node_modules/@babel/core/lib/config/full.js:43:39)
    at transformSync (/Users/b/Documents/Travis/t4/node_modules/@babel/core/lib/transform.js:41:38)
    at Object.transform (/Users/b/Documents/Travis/t4/node_modules/@babel/core/lib/transform.js:22:38)
    at resolve (/Users/b/Documents/Travis/t4/node_modules/@ember/test-helpers/node_modules/broccoli-babel-transpiler/lib/worker.js:11:29)

=================================================================================


It seems relevant that this is the same error reported [here](https://github.com/yapplabs/ember-modal-dialog/issues/268) with `ember-modal-dialog`. I’ll mention this there too as it may help solve both problems.

I’m able to replicate with these commands, with npm 6.4.1 installed:

git clone https://github.com/travis-ci/travis-web.git
cd travis-web
git checkout 99cce75
npm install
ember build -prod

What’s been particularly confusing is that I spent some time trying to narrow down which version of ember-intercom-io started production builds to fail; my guess was 1.1.2, which included an update of ember-cli-babel, but when I changed the package.json to use the mike-north/ember-intercom-io#v… style because of the missing versions on npm, the problem went away…! And then I could even put 1.1.5 in package.json and get a successful build locally, but then deployment would still fail… So I can’t be sure when the problem really started.

Let me know if I can provide any other information. Thanks for your work on this addon, it’s been useful for us!

An in-range update of ember-cli-qunit is breaking the build 🚨

Version 4.3.1 of ember-cli-qunit was just published.

Branch Build failing 🚨
Dependency ember-cli-qunit
Current Version 4.3.0
Type devDependency

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

ember-cli-qunit 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.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Cannot destroy component

The intercom-io component is working great! All messages are showing up on my intercom instance. However, when I leave the route on my site that renders the {{intercom-io}} component I get the following error.

Uncaught TypeError: Cannot read property 'appId' of null

The stack trace looks deep in the intercom js lib, so I'm having a hard time finding out what's causing it. Looks related to the shutdown api: https://github.com/mike-north/ember-intercom-io/blob/master/addon/services/intercom.js#L70

Support language_override config parameter

We wanted to use the language_override (mentioned here) to make the messenger appear in the same interface language as our webpage. This wasn't supported in this package so we created PR #465.

Is this something you could add to the main package?

An in-range update of ember-cli-uglify is breaking the build 🚨

Version 2.0.2 of ember-cli-uglify was just published.

Branch Build failing 🚨
Dependency ember-cli-uglify
Current Version 2.0.0
Type devDependency

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

ember-cli-uglify 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.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 6 commits.

  • bb9c69b release v2.0.2 🎉
  • 5920e86 Merge pull request #36 from ember-cli/ci
  • df6ab75 add test (basically, a default app built’s tests run even post uglification)
  • 16d749e Merge pull request #34 from Duder-onomy/upgrade-broccoli-uglify-sourcemap-to-2.0.1
  • fb1da04 fix CODE_OF_CONDUCT.md
  • 6284038 Updates broccoli-uglify-sourcemap to version 2.0.1

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot 📦🚀

Does not load

I've followed the default installation instructions carefully and the component is not loading. Further, it doesn't show any errors in the console (or anywhere else I can see).

That said, if I set the deferReadinessUntilLoaded to true then I receive this error:

ember.debug.js:19157 TypeError: Cannot read property 'then' of undefined at Object.initialize (ember-intercom.js:23)

Any pointers on debugging?

thanks

Ember link-to's (Transitions) not firing update in intercom

Hi!

So I'm having problems with intercom getting updated on ember transitions.

When I click any ember link-to's and transition the log is showing but intercom is not getting notified of the route change.

// router.js
sessionUser: inject.service(),
intercom: inject.service(),

didTransition() {
  this._super(...arguments);
  this.updateIntercom()
},
updateIntercom() {
  let user = this.get('sessionUser.currentUser')

  if(user) {
    let props = {
      name: user.get('name'),
      user_id: user.get('id'),
      email: user.get('email'),
      createdAt: user.get('createdAt'),
      userHash: user.get('intercomUserHash')
    }
    this.get('intercom').update(props)
    console.log('hello route change')
  }
},

I've also tried the below, with no luck:

updateIntercom() {
  let user = this.get('sessionUser.currentUser')

  if(user) {            
    this.get('intercom').update()      
  }
}

Any ideas?

An in-range update of ember-cli-htmlbars-inline-precompile is breaking the build 🚨

Version 1.0.3 of ember-cli-htmlbars-inline-precompile was just published.

Branch Build failing 🚨
Dependency ember-cli-htmlbars-inline-precompile
Current Version 1.0.2
Type devDependency

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

ember-cli-htmlbars-inline-precompile 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.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 13 commits.

  • 53b149e v1.0.3
  • f3155bc Add v1.0.3 to CHANGELOG.md.
  • c96406f Merge pull request #106 from rwjblue/update-babel-plugin-htmlbars-inline-precompile
  • 08180bc Update minimum version of heimdalljs-logger.
  • a2859db Update minimum version of hash-for-dep.
  • f57adb6 Update minimum version of ember-cli-version-checker.
  • f32cb07 Update minimum versions of dependencies.
  • a3578ed Merge pull request #104 from Turbo87/eslint
  • 195a1e3 Replace JSHint with ESLint
  • 9a931d1 Merge pull request #103 from Turbo87/chrome
  • 20b0c7c Use headless Chrome for testing
  • 19a5f95 Merge pull request #102 from Turbo87/module-paths
  • f33b729 Add support for importing from ember-cli-htmlbars-inline-precompile

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of ember-resolver is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 4.5.1 of ember-resolver was just published.

Branch Build failing 🚨
Dependency ember-resolver
Current Version 4.5.0
Type devDependency

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

ember-resolver 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.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 22 commits.

  • 4fbf54a v4.5.1
  • 0d3a85d Merge pull request #225 from ember-cli/expandLocalLookup
  • 338680a Implement MU sources and namespaces with expandLocalLookup
  • ecc4748 glimmer-resolver v0.4.3
  • 04f47d5 Add new types for new Ember releases
  • d7dc4dd Merge pull request #224 from 201-created/isaac/fallback-normalization
  • e38f353 normalize specifiers before passing to fallback
  • 13f05eb Merge pull request #221 from 201-created/isaac/fix-main-service-lookup
  • b2357af Merge pull request #222 from SergeAstapov/document-pluralizedTypes
  • 000bc2b [DOCS] Adds example about pluralizedTypes usage
  • 9b5e679 fix requires registry for main services/components
  • 9937486 Add template-options type to config
  • 7f3fbcf Merge pull request #220 from 201-created/isaac/namespace-argument
  • b57afa8 Add tests for main add-on lookup
  • 50036c2 glimmer-wrapper resolver to take targetNamespace

There are 22 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Standard usage pattern and registering users

Hi,

Just curious whether standard usage for this would be to inject the {{ember-intercom-io}] component into the application.hbs if you want to use intercom throughout your app?

I'm asking because I load the registered user in asynchronously and the ember-intercom-io component has already initialised at this point, so I'm using the following code to stop and start the intercom service once the registered user details are available. Does this make sense, or am I missing something?

loadCurrentUser: function() {
  if (this.get('session.isAuthenticated')) {      

    var currentUserId = this.get('session.session.content.authenticated.id');
    var user = this.store.findRecord('user', currentUserId).then(user => {

      this.get('intercom').set('user.name', user.get('name'));
      this.get('intercom').set('user.email', user.get('email'));
      this.get('intercom').set('user.createdAt', 1447135065173);              
      this.get('intercom').stop();
      this.get('intercom').start();
      this.set('session.currentUser', user);        
    })
  }
}.observes('session.isAuthenticated')

custom attributes

First, thanks for the great addon!

Is there a method to set custom attributes on the user? Currently, it seems that I can only set name, email and created_at.

I'd also like to be able to set the company, but it doesn't seem to work.

Thanks!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.