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

alternative: web extension #42

Open
abhijithvijayan opened this issue Jan 16, 2020 · 4 comments
Open

alternative: web extension #42

abhijithvijayan opened this issue Jan 16, 2020 · 4 comments

Comments

@abhijithvijayan
Copy link

abhijithvijayan commented Jan 16, 2020

As this project seems to be deprecated. I build another starter with webpack that can build cross browser extension as well. (This repo takes the inspiration)

Its got

  • webpack/html/sass/javascript
  • webpack/react/sass/typescript

Combo as well

https://github.com/abhijithvijayan/web-extension-starter

@hhaoao
Copy link

hhaoao commented Jan 30, 2020

@abhijithvijayan I looked at your project and found that the project built with the yarn package management tool, do you plan to consider creating a branch built on npm?

@abhijithvijayan
Copy link
Author

abhijithvijayan commented Jan 30, 2020

@hhaoao switching to npm is not that hard.

I personally prefer yarn over npm as it is much faster.

The repo now is set to use yarn v1 (for now)
Yarn v2 has breaking changes but is considered to be way faster than yarn v1

If you still wanna use npm instead of yarn, feel free to fork it and customize your own as it is a starter for all folks which is flexible.

I am working on an issue on the repo now.

I can create a branch for npm as well.
All it takes is deleting .yarn, yarn.lock, .yarnrc.yml and run npm install

Also, updating scripts from yarn something to npm something

Submit a PR if you can.

Also, feel free to raise an issue on the repo for this issue.

@hhaoao
Copy link

hhaoao commented Jan 31, 2020

@abhijithvijayan I follow your prompt to delete the relevant files and modify the package.json file:

"build": "npm run build:chrome && npm run build:firefox && npm run build:opera"

But I'm having a small problem,if you know how to fix it please let me know. (I don't know if I'm going to encounter it with yarn),Source map error problems have kept me at bay.

Source map error: Error: NetworkError when attempting to fetch resource.
Resource URL: moz-extension://f3e071f8-a623-4e01-9f41-8c1d7afeec8e/js/contentScript.bundle.js
Source Map URL: browser-polyfill.js.map

I didn't modify travis.yml file because I didn't use 'travis-ci'.
Tomorrow I'll revise the readme.md to submit a PR.

@abhijithvijayan
Copy link
Author

Please migrate this issue to the original repo

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