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

Include parse-latest.js within a dist/ directory of the repo #26

Closed
tomardern opened this issue Sep 28, 2015 · 7 comments
Closed

Include parse-latest.js within a dist/ directory of the repo #26

tomardern opened this issue Sep 28, 2015 · 7 comments

Comments

@tomardern
Copy link

Hi,

I'm currently developing a method to carry out Unit tests on Cloud Code (Something I will probably open source), and was utilising parse-latest.js to include Parse specific functions.

Each time the repo is updated, are you able to include pre-built "parse-latest.js" files for React/Node/Browser, therefore users will not have the trouble of building the files through gulp each time?

Thanks,

@andrewimm
Copy link
Contributor

Can you explain why you need a built copy for your unit tests? We would like to avoid shipping bundled versions of the SDK in npm module, as this can encourage antipatterns. Are you running them in a browser, or in node?

Sounds like you could use the latest version of our SDK available from our Downloads page, or from our CDN: www.parsecdn.com/js/parse-latest.js

@andrewimm
Copy link
Contributor

@simonbengtsson moving discussion here.

I actively use npm as a frontend package manager, and I believe developers who do the same will be using tools like Browserify or Webpack to compile their projects. If we were to include a compiled version in the npm module, how would you use it in a project? I'd like to understand this use case better.

@simonbengtsson
Copy link

Sure! I think that with the release of npm 3 many more people will start using npm as a front end package manager. One use case would be to upload the entire node_packages folder and reference scripts like <script src="node_modules/jquery/dist/jquery.js"></script>. I have seen this often with bower packages. The use case I had however was that I didn't use browserify and simply wanted to move all plain browser javascript dependencies to my dist folder.

In short provide the same functionality as repos like this one https://github.com/rabidaudio/bower-parse.

@andrewimm
Copy link
Contributor

I see. We used to ship both lib/ and dist/ for our Parse+React package, but removed it after a few months as it seemed cluttered. I can understand your argument though, and we definitely don't want to stand in the way of your development. It's no harder to enable this, since we already produce the file at publish time. I'll add an entry to the "files" field on package.json

@andrewimm
Copy link
Contributor

Included in 1.6.4, which just went to npm

@tomardern
Copy link
Author

I'm using Karma to carry out unit tests on my Parse Code. As it runs within a browser environment, it's much easier and simpler to inject Parse-latest.js into the page rather than compiling from source.

Thanks for sorting this :)

@simonbengtsson
Copy link

I have been really impressed with the parse team lately. You guys rock, and thanks for this!

@rabidaudio rabidaudio mentioned this issue Dec 8, 2015
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

3 participants