Pods compatibility.

Open
#3 4 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
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, webpack
Domain
frontend, tooling

Research direction

Start by examining how the resolver handles the pod paths components/componentName/template.hbs and components/componentName/component.coffee. Compare its behavior with ember-cli/ember-resolver before deciding whether that implementation is the right reference. Done means components using this pod layout resolve correctly in the webpack-based Ember CLI app.

Written by the indexing model from the issue text.

Description

I've almost managed to convert my Ember-CLI app to use webpack/gulp using this resolver. I'm about to go down the road of making components/pods work in our app.

components/componentName/template.hbs
components/componentName/component.coffee

Any thoughts?

I'm considering reimplementing this on top of https://github.com/ember-cli/ember-resolver instead of DefaultResolver.

Dominant language
JavaScript
Stars
31
Forks
8
Avg merge
6h 58m
Merged PRs (30d)
3

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.

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.