lifeart / lifeart/ember-cli-fallback-builds

Error regarding missing directory

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

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
23
Forks
1
PR merge metrics
No merged PRs in 30d

Description

I was trying this out and got the following error when running `ember build:fallback -prod`:

``` - broccoliBuilderErrorStack: [undefined]
- codeFrame: [undefined]
- errorMessage: Directory not found: /var/folders/n0/1cj2fwvj7hggltr7zqn8g9v40000gp/T/tmp-78479hej9tIuSzYm1/legacy
- errorType: [undefined]
- location:
- column: [undefined]
- file: [undefined]
- line: [undefined]
- message: Directory not found: /var/folders/n0/1cj2fwvj7hggltr7zqn8g9v40000gp/T/tmp-78479hej9tIuSzYm1/legacy
- name: BuilderError
- nodeAnnotation: [undefined]
- nodeName: [undefined]
- originalErrorMessage: [undefined]
- stack: BuilderError: Directory not found: /var/folders/n0/1cj2fwvj7hggltr7zqn8g9v40000gp/T/tmp-78479hej9tIuSzYm1/legacy
at Builder.checkInputPathsExist (/Users/meirish/code/vault/ui/node_modules/broccoli/lib/builder.js:261:15)
at new Builder (/Users/meirish/code/vault/ui/node_modules/broccoli/lib/builder.js:65:10)
at buildsMerger (/Users/meirish/code/vault/ui/node_modules/ember-cli-fallback-builds/lib/utils/builds-merger.js:48:19)
at BuildTask.run (/Users/meirish/code/vault/ui/node_modules/ember-cli-fallback-builds/lib/tasks/build.js:85:16)
at Promise.resolve.then (/Users/meirish/code/vault/ui/node_modules/ember-cli/lib/models/command.js:243:46)
at tryCatcher (/Users/meirish/code/vault/ui/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:323:19)
at invokeCallback (/Users/meirish/code/vault/ui/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:495:31)
at /Users/meirish/code/vault/ui/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:559:14
at flush (/Users/meirish/code/vault/ui/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:2402:5)
at process._tickCallback (internal/process/next_tick.js:61:11)```

Contributor guide

Open the contributing guide

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.

Research direction

Reproduce `ember build:fallback -prod` and trace the missing `legacy` path through `ember-cli-fallback-builds/lib/utils/builds-merger.js` and `lib/tasks/build.js`, then compare it with Broccoli's input-path check. Done means the command no longer fails with `Directory not found` for the generated legacy path.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.