Skip to content
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.

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

Resolve full, absolute paths to fix build issue #52

Merged
merged 1 commit into from Oct 19, 2015

Conversation

EranSch
Copy link

@EranSch EranSch commented Oct 19, 2015

gulp build was failing, providing the following error:

➜  ng6-starter-jspm git:(jspm) ✗ gulp build
[06:24:53] Using gulpfile ~/Repos/ng6-starter-jspm/Gulpfile.js
[06:24:53] Starting 'build'...
[06:24:53] 'build' errored after 317 ms
[06:24:53] Error on fetch for client/app/app.js at file:///Users/eschoellhorn/Repos/ng6-starter-jspm/client/client/app/app.js
    Error: ENOENT: no such file or directory, open '/Users/eschoellhorn/Repos/ng6-starter-jspm/client/client/app/app.js'
    at Error (native)

It seems that JSPM was preprending the root path (perhaps from its config?) to the app's entry point. Adding path.resolve to the gulpfile's resolveTo function results in absolute paths being returned. This resolved the problem I was having.

@PatrickJS
Copy link
Owner

thanks!

PatrickJS added a commit that referenced this pull request Oct 19, 2015
Resolve full, absolute paths to fix build issue
@PatrickJS PatrickJS merged commit 3074d7c into PatrickJS:jspm Oct 19, 2015
@EranSch EranSch deleted the use-full-paths branch October 19, 2015 11:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants