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

Why we should not use Bower but Yarn, while both download different codes for the same package? #16

Open
notalentgeek opened this issue Oct 29, 2017 · 2 comments

Comments

@notalentgeek
Copy link

For example:

yarn add babel
bower install babel

I have application running without server (I don't plan to use NodeJS as my back-end). It is now pure-front-end double-click HTML file.

I tried to import browser.js into my HTML file to be able to process JSX.

  • Import with <script src="node_modules/babel-core/lib/api/browser.js"> does not work.
  • But, import with <script src="bower_components/babel/browser.js"> works.

I do not want to download JavaScript manually from CDN. Because with Bower, it was not even a thing to do.

Apparently, the codes are different. Since, Bower is dead and it suggests its users to use Yarn, how can the codes be different?

How can I use Yarn like I use Bower?

@sheerun
Copy link
Owner

sheerun commented Oct 29, 2017 via email

@notalentgeek
Copy link
Author

How can I use Webpack? Specifically for this browser.js? I have tried to use ../.bin/webpack index.js babel.test.js I ran Webpack from node_modules/.bin but there are some "compilation" errors and the .js file is not usable.

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

2 participants