vernak2539
PD🧩 Plasmo Developers
•Created by vernak2539 on 9/17/2024 in #👟framework
Publishing to Multiple Markets using @PlasmoHQ/bpp github action
I've not gotten the sentry stuff to work yet for FF in the github action, but that's my fault in the way of building it... so once i get the new version approved in chrome, I'll be trying again
21 replies
PD🧩 Plasmo Developers
•Created by vernak2539 on 9/17/2024 in #👟framework
Publishing to Multiple Markets using @PlasmoHQ/bpp github action
Just an update here, I've ended up being able to publish it to the firefox add on store via the github action 🎉
21 replies
PD🧩 Plasmo Developers
•Created by vernak2539 on 9/17/2024 in #👟framework
Publishing to Multiple Markets using @PlasmoHQ/bpp github action
Cool thanks! I'll have a go with the new version and see what happens
21 replies
PD🧩 Plasmo Developers
•Created by vernak2539 on 9/17/2024 in #👟framework
Publishing to Multiple Markets using @PlasmoHQ/bpp github action
@tbrockman have you had any problems publishing to the Firefox add-on store? I see the links you put for your
prune repo and seems like you are publishing an addon.
But, I've come across issues that allude to problems due to source code concerns mozilla have.
I've submitted my extension to the add-on store manually for the first time and had to upload source code as well in one of the steps.21 replies
PD🧩 Plasmo Developers
•Created by vernak2539 on 9/17/2024 in #👟framework
Publishing to Multiple Markets using @PlasmoHQ/bpp github action
yeah... wrap is depcreated in v8 and you have to use try/catch... it was an interesting update
21 replies
PD🧩 Plasmo Developers
•Created by vernak2539 on 9/17/2024 in #👟framework
Publishing to Multiple Markets using @PlasmoHQ/bpp github action
Yeah, I think I could help with that as well.
I upgrade to v8 of sentry and they make differentiations that chrome extensions should follow so they don't collide with the global namespace of the webpage (i.e. fi the website is using sentry as well, there may be some conflicts). They talk about it here.
The interesting part is that error boundaries don't really allow for custom clients (if I understood it correctly), so I had to create my own.
21 replies
PD🧩 Plasmo Developers
•Created by vernak2539 on 9/17/2024 in #👟framework
Publishing to Multiple Markets using @PlasmoHQ/bpp github action
So yeah, let me try to break it down a bit more. Sentry is a bit confusing.
Okay, so Sentry has projects. Projects have releases. Releases have sourcemaps associated to them. In order to get the most out of Sentry, you want to
1. Create a release in your code (via tag or something)
2. Build your app
3. Create a release in sentry
4. Upload your build app's sourcemaps
5. Run your app with the release version in the
init function of sentry
This will make everything link together. The other way, which works not all of the time, is that you don't upload your sourcemaps and sentry tries to generate the release from the init and "download" your sourcemaps when the error happens.
So, when you build your app you get sourcemaps. The problem becomes that if I build my app for two targets, two sets of sourcemaps are generated.
You can see this you build for chrome then firefox and look in the directories. The cache buster inserted into filenames is different, yet they are the same app.
So, to get it work, sentry needs to know about all sourcemaps that are generated for each build/target environment.
I think it would be fine to upload all that stuff when creating the release, as you can upload them from multiple locations.21 replies
PD🧩 Plasmo Developers
•Created by vernak2539 on 9/17/2024 in #👟framework
Publishing to Multiple Markets using @PlasmoHQ/bpp github action
Yeah, it can be. Just need to build it multiple times, upload both outputs, then package both prior to publishing
21 replies
PD🧩 Plasmo Developers
•Created by vernak2539 on 9/17/2024 in #👟framework
Publishing to Multiple Markets using @PlasmoHQ/bpp github action
And you're right, it's likely much safer to build an artifact per publish...
The thing I'm getting to now though is that I use Sentry for error monitoring and have to upload sourcemaps. If I have different builds, then I have to upload more and more sourcemaps.
I guess it's not the end of the world, but would be nice not to have to do that
21 replies
PD🧩 Plasmo Developers
•Created by vernak2539 on 9/17/2024 in #👟framework
Publishing to Multiple Markets using @PlasmoHQ/bpp github action
@tbrockman thanks for the info! do you happen to know how I can find out about functionality that is target specfic?
21 replies
PD🧩 Plasmo Developers
•Created by lab on 4/3/2023 in #🔰newbie
Production Source Map?
thanks! i ended up finding them in the docs as well. i was stuck on the "development sourcemaps" page when i asked that question. just needed to go a bit further!
4 replies
PD🧩 Plasmo Developers
•Created by vernak2539 on 3/30/2023 in #🔰newbie
Error Monitoring and Metric Gathering
ohh nice, very interesting. I'll have a look. Thanks so much!
20 replies
PD🧩 Plasmo Developers
•Created by vernak2539 on 3/30/2023 in #🔰newbie
Error Monitoring and Metric Gathering
Yeah that doesn't sound the best. I really want to just know that it's not working so I can fix it. I can always test it every so often (or a lot as I use it everyday), but seems like error monitoring would be nice to have
20 replies
PD🧩 Plasmo Developers
•Created by vernak2539 on 3/30/2023 in #🔰newbie
Error Monitoring and Metric Gathering
Ahh that's super interesting! Thanks for all the information, will very much have to take into account all this stuff.
@avi12 just to make sure I understand, if my chrome extension wants to contact an API, I'd have to whitelist that somehow?
@stefan Do you have an example of what a Sentry and/or Posthog integration would look like with Plasmo?
20 replies