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

0.16.0: jspm build command fails #1030

Closed
OrKoN opened this issue Aug 18, 2015 · 7 comments
Closed

0.16.0: jspm build command fails #1030

OrKoN opened this issue Aug 18, 2015 · 7 comments

Comments

@OrKoN
Copy link
Contributor

OrKoN commented Aug 18, 2015

In a new jspm project:

$ jspm build
Transpile ES6? [yes]:
Minify? [yes]:no

err  AssertionError: rimraf: missing path
         at rimraf (/home/alex/.npm-packages/lib/node_modules/jspm/node_modules/rimraf/rimraf.js:47:3)
         at lib$rsvp$node$$tryApply (/home/alex/.npm-packages/lib/node_modules/jspm/node_modules/rsvp/dist/rsvp.js:1376:11)
         at lib$rsvp$node$$handleValueInput (/home/alex/.npm-packages/lib/node_modules/jspm/node_modules/rsvp/dist/rsvp.js:1476:20)
         at fn (/home/alex/.npm-packages/lib/node_modules/jspm/node_modules/rsvp/dist/rsvp.js:1464:18)
         at /home/alex/.npm-packages/lib/node_modules/jspm/lib/core.js:93:23
         at runMicrotasksCallback (node.js:337:7)
         at process._tickCallback (node.js:355:11)

P.S. is it documented somewhere?

@guybedford
Copy link
Member

This used to be used to provide transpilation, but has been left to deprecate. We can get this function going again for 0.17 though.

@jatsrt
Copy link

jatsrt commented Oct 1, 2015

So, as a new user, that is getting this same error, is there a workaround?

@whistler
Copy link

whistler commented Oct 1, 2015

@jatsrt you probably want to use the jspm bundle command instead

@masaeedu
Copy link

@whistler Yes, but that command no longer asks you whether you want to transpile ES6, it just chokes when it encounters it. How do I transpile my ES6?

@whistler
Copy link

@masaeedu It doesn't ask the question again because it generates configuration files(package.json/config.js) that save your selection.

The original bug report uses the jspm build command which I am not sure should still be used, I was not able to find documentation for it, but running jspm bundle to build produces the above error if the command is not provided further arguments i.e. the names of the source file and the destination file: jspm bundle app/main build.js.

@jperl
Copy link

jperl commented Oct 1, 2016

Does bundle optimize with rollup? The docs say to use jspm build for that?

@jperl
Copy link

jperl commented Oct 1, 2016

Nevermind. This error does not happen for me in 0.17.0-beta.29.

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

No branches or pull requests

6 participants