pre-enhanced app distributions
See original GitHub issuethis has been created as a sister-issue to https://github.com/davidbailey00/notion-deb-builder/pull/18 so it won’t be forgotten.
after the module rework in v0.11.0 is done, it would be possible to create and distribute pre-enhanced installers for notion. this could definitely be done with the deb builder, but i’m not sure yet if could be done for macOS/windows (or if it needs to be done?).
in theory it would just need: copying the app folder to make an
app.bak
, appending a singlerequire()
statement to every js file in theapp
folder, and adding in anenhancer
folder at the same level as theapp
folder.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Distribute pre-release versions of your app to your trusted testers
Firebase App Distribution allows developers to send pre-release versions of their app to trusted testers from the console or using command line tools, ......
Read more >z/OS UNIX Security Fundamentals - IBM Redbooks
A unified file system to represent data, programs, and any input or output ports used to transfer data as files, nested in directories,...
Read more >Distribute - Visual Studio App Center - Microsoft Learn
App Center Distribute is a tool for developers to quickly release builds to end user devices. Distribute supports Android, iOS, macOS, UWP, WPF ......
Read more >Contributing - notion-enhancer
If you installed a pre-enhanced app, create an issue in the notion-enhancer/notion-repackaged repository. · If you installed a browser extension, create an issue ......
Read more >Managing your App Distribution with Firebase | by Nabil Kazi
In this article, I would be covering the distribution of both Android and iOS apps using one single unified platform, Firebase App Distribution....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
a couple relevant updates:
i have added a
--path=</path/to/notion/resources/>
option, but the default is still the normal automatic platform detection.so that modules can be updated/installed without having to update the whole enhancer, they’ll be loaded from github and cached rather than distributed with the npm package (managed from the enhancer’s menu).
i had originally planned for that cache to be in
~/.notion-enhancer
, but i did some testing to see if it would work to just add an option to install in “portable” mode and stick the cache somewhere in the notion source, and it wouldn’t really. that would mean that if notion ever updates it would be deleted and users would not only have to reinstall the enhancer but also redownload and reconfigure all their modules.it’s not a massive issue, i can stick with the
~/.notion-enhancer
plan and just not use that cache duringnotion-enhancer apply
, but it does mean that installations and pre-enhanced distributions can’t come with any non-core mods pre-downloaded.@davidbailey00 yes - by including it in every js file,
module.export
functions can be overridden (for things like e.g. creating system menus or windows), and things can be run in/at different processes/times/places (e.g. main and renderer, in the host window or the notion webview).node_modules
is a good thought.