-
Notifications
You must be signed in to change notification settings - Fork 2
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
Make the plugin compatible with Snowpack v3.x #6
Comments
Would be looking to tackle this as I am trying to set up a smooth pipeline for building out a web extension. Are you still interested in maintaining this plugin @AWolf81? |
Yes, sounds great. I'd be happy to review your PR and merge it. |
I was trying to specify a local dependency using your example repo https://github.com/AWolf81/snowpack-chrome-preact-popup-demo I'd like to not have to push every time just to get a testing pipeline going, so I was wondering how exactly this can be set up? The fact that I get the second error leads me to believe the path is correct, so I think I need some configuration change, and not a path fix. EDIT: Immediately after asking this I realized that I can use the |
Yes, that's right. For me the development is working like this:
Note: The (I couldn't get it to work with the |
I've created an issue in snowpack discussions here As a work around, use buildOptions.clean in the user's snowpack config to just stop snowpack from cleaning. Changes still need to be made to make a fallback, but it is a minor rechanging of properties that I can submit a pr for. But what I would like to find is a fix that doesn't require disabling the cleaning process.
|
As mentioned in issue #5.
The current web-ext plugin only works on 2.x API.
To make it compatible the following point require changes:
config.installOptions.cwd
replace withconfig.root
env
fromconfig.installOptions.env
toconfig.packageOptions.env
manifest.json
copy from root folder to build - not sure why this is failingI'm trying to make it compatible v2.x and v3.x. I think that should be possible.
The text was updated successfully, but these errors were encountered: