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

Build/bundle CLI #706

Merged
merged 6 commits into from
Jun 9, 2016
Merged

Build/bundle CLI #706

merged 6 commits into from
Jun 9, 2016

Conversation

Rich-Harris
Copy link
Contributor

See #700

@@ -7,3 +7,4 @@ _actual
coverage
.commithash
.idea
bin/rollup
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Untrack file to ignore.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops! done, thanks

import { resolve } from 'path';
import relative from 'require-relative';
import handleError from './handleError';
import SOURCEMAPPING_URL from './sourceMappingURL.js';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sourceMappingUrl.js

@Rich-Harris Rich-Harris merged commit d5e1373 into master Jun 9, 2016
@Rich-Harris Rich-Harris deleted the gh-700 branch June 9, 2016 20:56
@snuggs
Copy link

snuggs commented Aug 29, 2016

Didn't know where to ask this but at the source. :-) @Rich-Harris curious about this line. Why can't we import? https://github.com/rollup/rollup/blame/master/bin/src/runRollup.js#L6

@Rich-Harris
Copy link
Contributor Author

@snuggs IIRC it's because things used to get terribly confusing if you had an import that was relative to the output bundle – Rollup would try and resolve it relative to the source file and all hell would break loose (but if the import was relative to the source file, the require statement in the CommonJS bundle would be incorrect). We had the same thing with Acorn and I did some really nasty stuff like this. Was fixed in #754, so we should be able to fix this now...

@Rich-Harris
Copy link
Contributor Author

Was fixed in #754, so we should be able to fix this now...

#886

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

3 participants