Skip to content

Common issues transfer #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Oct 11, 2018
Merged

Common issues transfer #12

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
1565329
Add common issues markdown from ember-cli.com
BradenLawrence Oct 4, 2018
800f9b0
Update internal link to the Windows Support section
BradenLawrence Oct 4, 2018
4434891
Modify common-issues.md content per @sandstrom's suggestions
BradenLawrence Oct 9, 2018
59b8829
Remove references to PhantomJS in the Docker section
BradenLawrence Oct 11, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
106 changes: 105 additions & 1 deletion guides/reference/common-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1,105 @@
<!-- copy over from ember-cli.com -->
### Don't install `npm` packages with `sudo`

Installing packages such as `bower` with `sudo` powers can lead to permissions
issues and ultimately to problems installing dependencies. See
[https://gist.github.com/isaacs/579814](https://gist.github.com/isaacs/579814)
for a collection of various solutions.

### Installing From Behind a Proxy

If you're behind a proxy, you might not be able to install because Ember CLI–or
some of its dependencies–tries to `git clone` a `git://` URL. (In this scenario,
only `http://` URLs will work).

You'll probably get an error like this:

```bash
npm ERR! git clone git://github.com/jgable/esprima.git Cloning into bare repository '/home/<username>/.npm/_git-remotes/git-git.colasdn.top-jgable-esprima-git-d221af32'...
npm ERR! git clone git://github.com/jgable/esprima.git
npm ERR! git clone git://github.com/jgable/esprima.git fatal: unable to connect to github.com:
npm ERR! git clone git://github.com/jgable/esprima.git github.com[0: 192.30.252.129]: errno=Connection timed out
npm ERR! Error: Command failed: fatal: unable to connect to github.com:
npm ERR! github.com[0: 192.30.252.129]: errno=Connection timed out
```

As a workaround you can configure `git` to make the translation:

```bash
git config --global url."https://".insteadOf git://
```

### Using Canary Build instead of release

In most cases you should use a stable release, but if you need to install a canary version to test beta features, you'd do it like this:

For Ember: `bower install ember#canary --resolution canary`
For `ember-data`: `npm install --save-dev emberjs/data#master`
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about some more color? E.g. "In most cases you should use a stable release, but if you need to install a canary version to test beta features, you'd do it like this:"


### Windows Build Performance Issues

See [The Windows Section](/release/reference/windows/) for more details.

### Cygwin on Windows

Node.js on Cygwin is no longer supported [more
details](https://github.com/nodejs/node/wiki/Installation#building-on-cygwin)
Rather then using Cygwin, we recommend running Ember CLI natively on windows,
or via the new [Windows Subsystem
Linux](https://msdn.microsoft.com/en-us/commandline/wsl/install_guide).

<!-- ### Usage with Docker -->
<!-- Possible topic for future development. -->


### Usage with Vagrant

[Vagrant](https://vagrantup.com) is a system for automatically creating and
setting up development environments that run in a virtual machine (VM).

Running your Ember CLI development environment from inside of a Vagrant VM will
require some additional configuration and will carry a few caveats.

#### Ports

In order to access your Ember CLI application from your desktop's web browser,
you'll have to open some forwarded ports into your VM. Ember CLI by default
uses two ports.

* For serving assets the default is `4200`. Can be configured via `--port 4200`.
* For live reload there is no default. Can be configured via `---live-reload-port=9999`.

To make Vagrant development seamless these ports will need to be forwarded.

```ruby
Vagrant.configure("2") do |config|
# ...
config.vm.network "forwarded_port", guest: 4200, host: 4200
config.vm.network "forwarded_port", guest: 9999, host: 9999
end
```

#### Watched Files

The way Vagrant syncs directories between your desktop and vm may prevent file
watching from working correctly. This will prevent rebuilds and live reloads
from working correctly. There are several work arounds:

1. Watch for changes by polling the file system via: `ember serve --watcher polling`.
2. Use [nfs for synced folders](https://docs.vagrantup.com/v2/synced-folders/nfs.html).

#### VM Setup

When setting up your VM, install Ember CLI dependencies as you normally would.
Some of these dependencies (such as [broccoli-sass](#sass)) may have native
depenencies that may require recompilation. To do so run:

```bash
npm rebuild
```

#### Provider

The two most common Vagrant providers, VirtualBox and VMware Fusion, will both
work. However, VMware Fusion is substantially faster and will use less battery
life if you're on a laptop. As of now, VirtualBox will use 100% of a single CPU
core to poll for file system changes inside of the VM.