I tried to follow the initial steps from here: https://www.learnstorybook.com/intro-to-storybook/react/en/get-started/

running:

npx create-react-app taskbox
cd taskbox

Then when I ran:
npx -p @storybook/cli sb init

I get the error TypeError: Cannot set property 'storybook' of undefined

This is the full message in my terminal:

 sb init - the simplest way to add a

Issue Summary

In Safari 13.0.4 on macOS 10.15.2, the 'Upload routes YAML' button triggers a file browser that only allows selection of files ending in .yml. These are not accepted by the application, which requires a .yaml extension. This results in routes not being uploadable with Safari.

To Reproduce

1. In Safari, click the 'Upload routes YAML' button in Labs.

This doesn'

Reference: https://github.com/emberjs/ember.js/pull/18239/files#r314775795

There seems to be a few examples of using custom components via render prop that mostly rely on 3rd parties like bootstrap, material, or other UI libraries. Are there any example of people using a custom component they've developed along with text-mask.

I'd like to get a better sense on the best way to set up my custom input components to make the integration process easier.

Modernization

As NODE 6 will be dropped soon, we would like to take this opportunity to upgrade the code-base to modern features, such as native promises and async/await.

Porting the code base to Native Promises, and async-await syntax will provide us with:

• better promise based async callstacks (in Node 12) and overall better debugging.

To accomplish this, we should (when possibl

The ember-data core team and contributors would like to modernize the API documentation by EmberConf 2020. Modernizing entails writing a package overview, revising inline documentation and auditing code snippets for accuracy. I broke the sections of this quest issue out by logical aspects of ember-data's API. Each section will list individual tasks.

[History](https://github.com/emberjs/data/i

We've integrated ember-simple-auth to our application. Following, the documentation, we load the user from the sessionAuthenticated callback :

// app/routes/application.js
import Ember from 'ember';
import ApplicationRouteMixin from 'ember-simple-auth/mixins/application-route-mixin';

const { service } = Ember.inject;

export default Ember.Route.extend(ApplicationRouteMixin

When developing locally, there are many YUIDoc warnings that say "Missing item type", like so:

WARNING:  ember-table/-private/utils/array.js:4: Missing item type
Genericizes `objectAt` so it can be run against a normal array or an Ember array
WARNING:  ember-table/-private/utils/array.js:32: Missing item type
Cycle shift an internal [start..end] to [start + 1...end, start].
WARNING:  e

Hi!

I've discovered that logging has changed with the addition of useLogger, but the documentation hasn't been updated to reflect this change.

Issue and Steps to Reproduce

• The first visit to "Routes" table, by selecting the "Routes" tab, displays an empty table and outputs a JS error:

This is likely a bug in the inspector itself.
You can report bugs at https://github.com/emberjs/ember-inspector.
Error message: routeHandler.get is not a function
Stack trace: TypeError: routeHandler.get is not a function
    at o.buildS

As you can see in the video, the positioning of the select options in the autocomplete chips dropdown (but also seen with the regular autocomplete) is more or less completely unusable. It appears to related to the keyboard and whatever the positioning computation is.

We should add some docs to let people know to write normal Ember tests and how we would recommend testing the electron parts.

I'm looking for a convention/standard to document components, especially targeting these information:

• arguments
• attributes
• yield

for components, template-only components while supporting for java- and typescript. Primarily focused for glimmer components, yet the js-only approach should also be suitable to be applied to ember components, too.

The idea is, that these conventions can

The issue template for this repo currently says:

Hello!

This isn’t the place for feature requests or bug reports. If that’s what you’ve come here for, please either visit our [public bug tracker](https://github.com/travis-ci/travis-ci/issues) or send us an email at support@travis-ci.org.

Otherwise, go ahead and delete this text :grimacing:

I read this as "this isn't the place

I think this is just me not seeing this in the documentation/issues anywhere...

But I ended up digging through the addon/modules trying to find out what property was being passed to selectedItemComponent.

An example of the selectedItemComponent component as well as some documentation would certainly be helpful to new / less competent users (yup, that's me :) ).

While I'm aware that pagination can be achieved via next and previous page. Right know it doesn't seem possible to go to a specific page number, as described in here.

I'll also cross-reference this Issue [from here](https://github.com/Shopify/js-buy-sdk/

Expected:
The documentation would be consolidated to one place and when new features are added/updated, they are added to the documentation.

Actual:
Right now, using ember-engines requires a bit of juggling between Github and the guides, which can give the impression that documentation is missing.

Proposed solution:

1. Make the README.md a table of contents and link to sec

Environment

• Mac OS: 10.14.6
• node: 8.16.2
• npm: 6.4.1

1. Test for Ember 2.18

npm install -g ember-cli@2.18
ember new test-ember-2-18
cd test-ember-2-18
ember i ember-bootstrap@3.1.0 ember-angle-bracket-invocation-polyfill@2.0.2

# copied from https://www.ember-bootstrap.com/api/classes/Components.Navbar.html
cat <<EOF > app/templates/application.hbs
<BsNavbar a

Environment

• Ember Version: n/a
• Ember CLI Version: n/a
• Ember CP Validations Version: n/a

Steps to Reproduce

On the documenation site, try searching for 'checkbox' or 'input'. Nothing happens.

I've just now realized it's because there were no results for 'checkbox' or 'input'. I'm going to leave this issue open because it does feel like the UX around searching the docs is