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

Browser Bundles links not working #35

Closed
hugooliveirad opened this issue Mar 9, 2016 · 12 comments
Closed

Browser Bundles links not working #35

hugooliveirad opened this issue Mar 9, 2016 · 12 comments

Comments

@hugooliveirad
Copy link

These links aren't working:

README.md point to them at the Browser Bundle section

@iamdustan
Copy link
Collaborator

Oops. @bpugh it seems like we need to keep the compiled build in the repo for that? Is that a requirement of npmcdn?

@iamdustan
Copy link
Collaborator

At first glance of npmcdn it looks like the dist should be published to npm. Can anyone verify that?

@bpugh
Copy link
Contributor

bpugh commented Mar 9, 2016

According to npmcdn docs they can be published under umd or dist folder.

@jquense
Copy link
Collaborator

jquense commented Mar 9, 2016

ya it wants a path to a browser dist build. its abit annoying to keep in the repo but probably worth it for this use case ?

@iamdustan
Copy link
Collaborator

Looking at the react-router repo itself, I didn’t see a dist/umd directory (unless I looked in the wrong place somehow). It seemed like it could just be published with that. I’d take publishing umd builds to npm over GH personally, but am open to popular opinion.

@bpugh
Copy link
Contributor

bpugh commented Mar 9, 2016

Yeah the whole point of npmcdn is that you only need to publish the dist files to npm and it pulls them in automagically

@jquense
Copy link
Collaborator

jquense commented Mar 9, 2016

oops yeah too early for me still. yeah we should only need to publish the dist files for npmcdn, no need to keep them in the repo

@iamdustan
Copy link
Collaborator

Preparing to publish 3.1.1 with dist in npm.

@bpugh
Copy link
Contributor

bpugh commented Mar 9, 2016

Yeah sorry should thought about that we would need to publish a new version to npm once we made that change.

@iamdustan
Copy link
Collaborator

@iamdustan
Copy link
Collaborator

Thanks for reporting @hugobessaa

@hugooliveirad
Copy link
Author

Thanks for fixing that 😄!

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

4 participants