Ember addons that use babel plugins cannot be developed on using `npm link` or `yarn link`

Open
#233 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
babel, javascript
Domain
build-system

Research direction

Reproduce the failure with ember new, a cloned addon such as ember-cli-imgix, npm link or yarn link, and ember serve; begin by inspecting how linked addons resolve Babel plugins. Done means the linked addon can be developed successfully and ember serve no longer reports unresolved Babel plugins, without relying on a commit-hash workaround.

Written by the indexing model from the issue text.

Description

(please let me know if this belongs somewhere else)

When I attempt to work on a ember addon by yarn link or npm link babel cannot resolve plugins.

Steps to reproduce:

  • ember new
  • git clone a ember addon with babel plugins ( ember-cli-imgix uses babel plugins ) git clone git@github.com:imgix/ember-cli-imgix.git
  • run npm link in the addons dir.
  • run npm link <addon name> in the newly created ember app.
  • run ember serve

Observe that ember cannot resolve the babel plugins.

My feeling is that it has something to do with: https://github.com/babel/babel-loader/issues/149#issuecomment-320581223
But I really don't know.

You might see something like:
image

My current workaround is to push the addon and consume it by commit hash.

Output from ember version --verbose && npm --version && yarn --version:

ember-cli: 3.0.4
http_parser: 2.8.0
node: 8.11.3
v8: 6.2.414.54
uv: 1.19.1
zlib: 1.2.11
ares: 1.10.1-DEV
modules: 57
nghttp2: 1.32.0
napi: 3
openssl: 1.0.2o
icu: 60.1
unicode: 10.0
cldr: 32.0
tz: 2017c
os: darwin x64
5.6.0
1.7.0
Dominant language
JavaScript
Stars
152
Forks
115
Avg merge
23h 22m
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from emberjs/ember-cli-babel

All issues in emberjs/ember-cli-babel

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.