2019-01-06 05:52:53 -08:00
Build status: [](https://circleci.com/gh/karlicoss/grasp)
2019-01-06 16:03:03 -08:00
Grasp is an [extension for Chrome ](https://chrome.google.com/webstore/detail/grasp-extension/ohhbcfjmnbmgkajljopdjcaokbpgbgfa ) (Firefox support is in progress), which adds a button/keybinding to capture current page title and url,
2019-01-06 14:15:53 -08:00
possibly selected text, additional comments or tags and send it into your [Org Mode ](https://orgmode.org/ ) file.
2019-01-06 05:52:53 -08:00
2019-01-06 15:22:31 -08:00
[See a short demo ](https://www.youtube.com/watch?v=Z8Bk-IazdGo ).
2019-01-06 14:15:53 -08:00
# Requirements
* `pip3 install --user hug` for [Hug ](http://www.hug.rest/ ) HTTP server.
Collapse boilerplate in a single commit
First prototype
Added the README
Fixed the hot module replacement
Minor adjustments on readme
Normalizing the env vars and using it capitalized
Added info about the react.js branch
Fix babel transpiling
Using yarn
Removing the babel package, just the babel-core does the job
Using just the dependencies key on package.json
Since it isn't a lib package doesn't matter the separation between
devDependencies and dependencies.
Updating the css-loader
Updating the fs-extra
Moving the utility packages to utils folder
Better description
Adds the license
closes #3
Write the env vars on the bundle file
http://dev.topheman.com/make-your-react-production-minified-version-with-webpack/
Fixs the hot reload setup
Sringifies the env object to define plugin
Uses the webpack html plugin to generate the pages in a less hacky way
Uses the write-file-webpack-plugin
this plugin allows the webpack write on disk all files, even running
with the webserver, which is necessary to the hot reload.
this plugin also help us to remove nasty hacks and expose bundles to
other extension features.
Allows exclude some entry points to be hot reloaded
It's useful for content scripts that can't keep the connection with the
webpack endpoint.
Updates the webpack
Updates the README with instructions about the content scripts
resolves #4
Updates to Webpack 2
closes #8
Expand the DefinePlugin usage
In Webpack 1, the replaced value at compile time by define plugin was placed with
parenthesis, like ({"NODE_ENV":"development","PORT":3000}), now, it not works in
this way, breaking the app.
So, to simplify the things, this commit just passes the NODE_ENV var.
Fix README
Exclude /node_modules/ from babel and css transpiling #9
Source maps to help debugging
closes #10
Removes the forbidden webpack config 'chromeExtensionBoilerplate'
before build and webserver's start
Although I know that it's not a good practice, right now I don't know a
good way to keep the boilerplate configs simple as it is today without
this hacky solution, so, until we came with a better solution, we'll
remove the key before build and webserver's start.
#9
Update README.md
Removing babel.js
Basically, we don't need transpiling with babel since Webpack 2 take care of
ES6 modules transpiling and the ES2015 is supported by Chrome.
kudos @gagarine
resolve #16
Setup boilerplate to load images and other assets in html and css
resolves #18
resolves #23
resolves #14
resolves #12
Added icons and images boilerplate
Split dependencies on package.json
resolves #15
Webpack config improvements (#26)
- Use CopyWebpackPlugin to generate `manifest.json` file
- Use CleanWebpackPlugin to clear build folder
Minor README adjustments
* explicitly the required node version
* pointing to yarn install instructions page instead suggest install
with npm. the yarn page will be always updated to the best way to install
the yarn.
closes #28
Adding the contribution guidelines
2016-04-14 06:16:50 -07:00
2019-01-06 14:15:53 -08:00
# Running
2019-01-07 14:53:08 -08:00
1. Install server counterpart as systemd service (to autostart it): `server/setup --path /path/to/your/capture.org [--port <custom port>]` .
Or alternatively, just run it directly if you don't want to autostart it: `server/grasp_server.py --path /path/to/your/capture.org [--port <custom_port>]` .
2019-01-06 14:15:53 -08:00
2. Install chrome extension and configure hotkeys
Collapse boilerplate in a single commit
First prototype
Added the README
Fixed the hot module replacement
Minor adjustments on readme
Normalizing the env vars and using it capitalized
Added info about the react.js branch
Fix babel transpiling
Using yarn
Removing the babel package, just the babel-core does the job
Using just the dependencies key on package.json
Since it isn't a lib package doesn't matter the separation between
devDependencies and dependencies.
Updating the css-loader
Updating the fs-extra
Moving the utility packages to utils folder
Better description
Adds the license
closes #3
Write the env vars on the bundle file
http://dev.topheman.com/make-your-react-production-minified-version-with-webpack/
Fixs the hot reload setup
Sringifies the env object to define plugin
Uses the webpack html plugin to generate the pages in a less hacky way
Uses the write-file-webpack-plugin
this plugin allows the webpack write on disk all files, even running
with the webserver, which is necessary to the hot reload.
this plugin also help us to remove nasty hacks and expose bundles to
other extension features.
Allows exclude some entry points to be hot reloaded
It's useful for content scripts that can't keep the connection with the
webpack endpoint.
Updates the webpack
Updates the README with instructions about the content scripts
resolves #4
Updates to Webpack 2
closes #8
Expand the DefinePlugin usage
In Webpack 1, the replaced value at compile time by define plugin was placed with
parenthesis, like ({"NODE_ENV":"development","PORT":3000}), now, it not works in
this way, breaking the app.
So, to simplify the things, this commit just passes the NODE_ENV var.
Fix README
Exclude /node_modules/ from babel and css transpiling #9
Source maps to help debugging
closes #10
Removes the forbidden webpack config 'chromeExtensionBoilerplate'
before build and webserver's start
Although I know that it's not a good practice, right now I don't know a
good way to keep the boilerplate configs simple as it is today without
this hacky solution, so, until we came with a better solution, we'll
remove the key before build and webserver's start.
#9
Update README.md
Removing babel.js
Basically, we don't need transpiling with babel since Webpack 2 take care of
ES6 modules transpiling and the ES2015 is supported by Chrome.
kudos @gagarine
resolve #16
Setup boilerplate to load images and other assets in html and css
resolves #18
resolves #23
resolves #14
resolves #12
Added icons and images boilerplate
Split dependencies on package.json
resolves #15
Webpack config improvements (#26)
- Use CopyWebpackPlugin to generate `manifest.json` file
- Use CleanWebpackPlugin to clear build folder
Minor README adjustments
* explicitly the required node version
* pointing to yarn install instructions page instead suggest install
with npm. the yarn page will be always updated to the best way to install
the yarn.
closes #28
Adding the contribution guidelines
2016-04-14 06:16:50 -07:00
2019-01-07 14:53:08 -08:00
That's it! **Currently port `12212` is hardcoded** in the extension, but it will be configurable later.
Collapse boilerplate in a single commit
First prototype
Added the README
Fixed the hot module replacement
Minor adjustments on readme
Normalizing the env vars and using it capitalized
Added info about the react.js branch
Fix babel transpiling
Using yarn
Removing the babel package, just the babel-core does the job
Using just the dependencies key on package.json
Since it isn't a lib package doesn't matter the separation between
devDependencies and dependencies.
Updating the css-loader
Updating the fs-extra
Moving the utility packages to utils folder
Better description
Adds the license
closes #3
Write the env vars on the bundle file
http://dev.topheman.com/make-your-react-production-minified-version-with-webpack/
Fixs the hot reload setup
Sringifies the env object to define plugin
Uses the webpack html plugin to generate the pages in a less hacky way
Uses the write-file-webpack-plugin
this plugin allows the webpack write on disk all files, even running
with the webserver, which is necessary to the hot reload.
this plugin also help us to remove nasty hacks and expose bundles to
other extension features.
Allows exclude some entry points to be hot reloaded
It's useful for content scripts that can't keep the connection with the
webpack endpoint.
Updates the webpack
Updates the README with instructions about the content scripts
resolves #4
Updates to Webpack 2
closes #8
Expand the DefinePlugin usage
In Webpack 1, the replaced value at compile time by define plugin was placed with
parenthesis, like ({"NODE_ENV":"development","PORT":3000}), now, it not works in
this way, breaking the app.
So, to simplify the things, this commit just passes the NODE_ENV var.
Fix README
Exclude /node_modules/ from babel and css transpiling #9
Source maps to help debugging
closes #10
Removes the forbidden webpack config 'chromeExtensionBoilerplate'
before build and webserver's start
Although I know that it's not a good practice, right now I don't know a
good way to keep the boilerplate configs simple as it is today without
this hacky solution, so, until we came with a better solution, we'll
remove the key before build and webserver's start.
#9
Update README.md
Removing babel.js
Basically, we don't need transpiling with babel since Webpack 2 take care of
ES6 modules transpiling and the ES2015 is supported by Chrome.
kudos @gagarine
resolve #16
Setup boilerplate to load images and other assets in html and css
resolves #18
resolves #23
resolves #14
resolves #12
Added icons and images boilerplate
Split dependencies on package.json
resolves #15
Webpack config improvements (#26)
- Use CopyWebpackPlugin to generate `manifest.json` file
- Use CleanWebpackPlugin to clear build folder
Minor README adjustments
* explicitly the required node version
* pointing to yarn install instructions page instead suggest install
with npm. the yarn page will be always updated to the best way to install
the yarn.
closes #28
Adding the contribution guidelines
2016-04-14 06:16:50 -07:00
2019-01-06 14:15:53 -08:00
# Motivation
Why use org-capture? Well, it's hard to explain, maybe some other time... However if you do know you want to use it instead/alongside your browser bookmarks, by default
you don't have much choice and have to copy everything manually. For an average Org Mode user it's a torture.
Collapse boilerplate in a single commit
First prototype
Added the README
Fixed the hot module replacement
Minor adjustments on readme
Normalizing the env vars and using it capitalized
Added info about the react.js branch
Fix babel transpiling
Using yarn
Removing the babel package, just the babel-core does the job
Using just the dependencies key on package.json
Since it isn't a lib package doesn't matter the separation between
devDependencies and dependencies.
Updating the css-loader
Updating the fs-extra
Moving the utility packages to utils folder
Better description
Adds the license
closes #3
Write the env vars on the bundle file
http://dev.topheman.com/make-your-react-production-minified-version-with-webpack/
Fixs the hot reload setup
Sringifies the env object to define plugin
Uses the webpack html plugin to generate the pages in a less hacky way
Uses the write-file-webpack-plugin
this plugin allows the webpack write on disk all files, even running
with the webserver, which is necessary to the hot reload.
this plugin also help us to remove nasty hacks and expose bundles to
other extension features.
Allows exclude some entry points to be hot reloaded
It's useful for content scripts that can't keep the connection with the
webpack endpoint.
Updates the webpack
Updates the README with instructions about the content scripts
resolves #4
Updates to Webpack 2
closes #8
Expand the DefinePlugin usage
In Webpack 1, the replaced value at compile time by define plugin was placed with
parenthesis, like ({"NODE_ENV":"development","PORT":3000}), now, it not works in
this way, breaking the app.
So, to simplify the things, this commit just passes the NODE_ENV var.
Fix README
Exclude /node_modules/ from babel and css transpiling #9
Source maps to help debugging
closes #10
Removes the forbidden webpack config 'chromeExtensionBoilerplate'
before build and webserver's start
Although I know that it's not a good practice, right now I don't know a
good way to keep the boilerplate configs simple as it is today without
this hacky solution, so, until we came with a better solution, we'll
remove the key before build and webserver's start.
#9
Update README.md
Removing babel.js
Basically, we don't need transpiling with babel since Webpack 2 take care of
ES6 modules transpiling and the ES2015 is supported by Chrome.
kudos @gagarine
resolve #16
Setup boilerplate to load images and other assets in html and css
resolves #18
resolves #23
resolves #14
resolves #12
Added icons and images boilerplate
Split dependencies on package.json
resolves #15
Webpack config improvements (#26)
- Use CopyWebpackPlugin to generate `manifest.json` file
- Use CleanWebpackPlugin to clear build folder
Minor README adjustments
* explicitly the required node version
* pointing to yarn install instructions page instead suggest install
with npm. the yarn page will be always updated to the best way to install
the yarn.
closes #28
Adding the contribution guidelines
2016-04-14 06:16:50 -07:00
2019-01-06 14:15:53 -08:00
For a while, I used [the only ](https://github.com/sprig/org-capture-extension ) Chrome extension for that (as for January 2019). However, it relies on setting up MIME
handler which is quite flaky for many people. What is more, capturing via org template requires always running emacs daemon, which might be too much for some people.
But the worst thing is if capturing fails, you have to way of knowing about it. After losing few days of captured stuff due to MIME handler mysteriously not working,
I got fed up and figured it's time to implement something more reliable.
Collapse boilerplate in a single commit
First prototype
Added the README
Fixed the hot module replacement
Minor adjustments on readme
Normalizing the env vars and using it capitalized
Added info about the react.js branch
Fix babel transpiling
Using yarn
Removing the babel package, just the babel-core does the job
Using just the dependencies key on package.json
Since it isn't a lib package doesn't matter the separation between
devDependencies and dependencies.
Updating the css-loader
Updating the fs-extra
Moving the utility packages to utils folder
Better description
Adds the license
closes #3
Write the env vars on the bundle file
http://dev.topheman.com/make-your-react-production-minified-version-with-webpack/
Fixs the hot reload setup
Sringifies the env object to define plugin
Uses the webpack html plugin to generate the pages in a less hacky way
Uses the write-file-webpack-plugin
this plugin allows the webpack write on disk all files, even running
with the webserver, which is necessary to the hot reload.
this plugin also help us to remove nasty hacks and expose bundles to
other extension features.
Allows exclude some entry points to be hot reloaded
It's useful for content scripts that can't keep the connection with the
webpack endpoint.
Updates the webpack
Updates the README with instructions about the content scripts
resolves #4
Updates to Webpack 2
closes #8
Expand the DefinePlugin usage
In Webpack 1, the replaced value at compile time by define plugin was placed with
parenthesis, like ({"NODE_ENV":"development","PORT":3000}), now, it not works in
this way, breaking the app.
So, to simplify the things, this commit just passes the NODE_ENV var.
Fix README
Exclude /node_modules/ from babel and css transpiling #9
Source maps to help debugging
closes #10
Removes the forbidden webpack config 'chromeExtensionBoilerplate'
before build and webserver's start
Although I know that it's not a good practice, right now I don't know a
good way to keep the boilerplate configs simple as it is today without
this hacky solution, so, until we came with a better solution, we'll
remove the key before build and webserver's start.
#9
Update README.md
Removing babel.js
Basically, we don't need transpiling with babel since Webpack 2 take care of
ES6 modules transpiling and the ES2015 is supported by Chrome.
kudos @gagarine
resolve #16
Setup boilerplate to load images and other assets in html and css
resolves #18
resolves #23
resolves #14
resolves #12
Added icons and images boilerplate
Split dependencies on package.json
resolves #15
Webpack config improvements (#26)
- Use CopyWebpackPlugin to generate `manifest.json` file
- Use CleanWebpackPlugin to clear build folder
Minor README adjustments
* explicitly the required node version
* pointing to yarn install instructions page instead suggest install
with npm. the yarn page will be always updated to the best way to install
the yarn.
closes #28
Adding the contribution guidelines
2016-04-14 06:16:50 -07:00
2019-01-06 14:15:53 -08:00
My approach still requires a running server, but it's a simple python script which simply appends a text entry to a text file. The backend always responds back and in case anything
fails, you get a notification.
Collapse boilerplate in a single commit
First prototype
Added the README
Fixed the hot module replacement
Minor adjustments on readme
Normalizing the env vars and using it capitalized
Added info about the react.js branch
Fix babel transpiling
Using yarn
Removing the babel package, just the babel-core does the job
Using just the dependencies key on package.json
Since it isn't a lib package doesn't matter the separation between
devDependencies and dependencies.
Updating the css-loader
Updating the fs-extra
Moving the utility packages to utils folder
Better description
Adds the license
closes #3
Write the env vars on the bundle file
http://dev.topheman.com/make-your-react-production-minified-version-with-webpack/
Fixs the hot reload setup
Sringifies the env object to define plugin
Uses the webpack html plugin to generate the pages in a less hacky way
Uses the write-file-webpack-plugin
this plugin allows the webpack write on disk all files, even running
with the webserver, which is necessary to the hot reload.
this plugin also help us to remove nasty hacks and expose bundles to
other extension features.
Allows exclude some entry points to be hot reloaded
It's useful for content scripts that can't keep the connection with the
webpack endpoint.
Updates the webpack
Updates the README with instructions about the content scripts
resolves #4
Updates to Webpack 2
closes #8
Expand the DefinePlugin usage
In Webpack 1, the replaced value at compile time by define plugin was placed with
parenthesis, like ({"NODE_ENV":"development","PORT":3000}), now, it not works in
this way, breaking the app.
So, to simplify the things, this commit just passes the NODE_ENV var.
Fix README
Exclude /node_modules/ from babel and css transpiling #9
Source maps to help debugging
closes #10
Removes the forbidden webpack config 'chromeExtensionBoilerplate'
before build and webserver's start
Although I know that it's not a good practice, right now I don't know a
good way to keep the boilerplate configs simple as it is today without
this hacky solution, so, until we came with a better solution, we'll
remove the key before build and webserver's start.
#9
Update README.md
Removing babel.js
Basically, we don't need transpiling with babel since Webpack 2 take care of
ES6 modules transpiling and the ES2015 is supported by Chrome.
kudos @gagarine
resolve #16
Setup boilerplate to load images and other assets in html and css
resolves #18
resolves #23
resolves #14
resolves #12
Added icons and images boilerplate
Split dependencies on package.json
resolves #15
Webpack config improvements (#26)
- Use CopyWebpackPlugin to generate `manifest.json` file
- Use CleanWebpackPlugin to clear build folder
Minor README adjustments
* explicitly the required node version
* pointing to yarn install instructions page instead suggest install
with npm. the yarn page will be always updated to the best way to install
the yarn.
closes #28
Adding the contribution guidelines
2016-04-14 06:16:50 -07:00
2019-01-06 14:15:53 -08:00
Extra collateral benefit is that you can potentially add anything as a backend, e.g. you might be more of a Markdown or Todo.txt fan (let me know if you are interested in that!).
Collapse boilerplate in a single commit
First prototype
Added the README
Fixed the hot module replacement
Minor adjustments on readme
Normalizing the env vars and using it capitalized
Added info about the react.js branch
Fix babel transpiling
Using yarn
Removing the babel package, just the babel-core does the job
Using just the dependencies key on package.json
Since it isn't a lib package doesn't matter the separation between
devDependencies and dependencies.
Updating the css-loader
Updating the fs-extra
Moving the utility packages to utils folder
Better description
Adds the license
closes #3
Write the env vars on the bundle file
http://dev.topheman.com/make-your-react-production-minified-version-with-webpack/
Fixs the hot reload setup
Sringifies the env object to define plugin
Uses the webpack html plugin to generate the pages in a less hacky way
Uses the write-file-webpack-plugin
this plugin allows the webpack write on disk all files, even running
with the webserver, which is necessary to the hot reload.
this plugin also help us to remove nasty hacks and expose bundles to
other extension features.
Allows exclude some entry points to be hot reloaded
It's useful for content scripts that can't keep the connection with the
webpack endpoint.
Updates the webpack
Updates the README with instructions about the content scripts
resolves #4
Updates to Webpack 2
closes #8
Expand the DefinePlugin usage
In Webpack 1, the replaced value at compile time by define plugin was placed with
parenthesis, like ({"NODE_ENV":"development","PORT":3000}), now, it not works in
this way, breaking the app.
So, to simplify the things, this commit just passes the NODE_ENV var.
Fix README
Exclude /node_modules/ from babel and css transpiling #9
Source maps to help debugging
closes #10
Removes the forbidden webpack config 'chromeExtensionBoilerplate'
before build and webserver's start
Although I know that it's not a good practice, right now I don't know a
good way to keep the boilerplate configs simple as it is today without
this hacky solution, so, until we came with a better solution, we'll
remove the key before build and webserver's start.
#9
Update README.md
Removing babel.js
Basically, we don't need transpiling with babel since Webpack 2 take care of
ES6 modules transpiling and the ES2015 is supported by Chrome.
kudos @gagarine
resolve #16
Setup boilerplate to load images and other assets in html and css
resolves #18
resolves #23
resolves #14
resolves #12
Added icons and images boilerplate
Split dependencies on package.json
resolves #15
Webpack config improvements (#26)
- Use CopyWebpackPlugin to generate `manifest.json` file
- Use CleanWebpackPlugin to clear build folder
Minor README adjustments
* explicitly the required node version
* pointing to yarn install instructions page instead suggest install
with npm. the yarn page will be always updated to the best way to install
the yarn.
closes #28
Adding the contribution guidelines
2016-04-14 06:16:50 -07:00
2019-01-06 14:15:53 -08:00
# Potentional improvements
* due to server counterpart, one could even run it elsewhere, not necessarily on localhost
* also see [todos ](./TODO.org )
Collapse boilerplate in a single commit
First prototype
Added the README
Fixed the hot module replacement
Minor adjustments on readme
Normalizing the env vars and using it capitalized
Added info about the react.js branch
Fix babel transpiling
Using yarn
Removing the babel package, just the babel-core does the job
Using just the dependencies key on package.json
Since it isn't a lib package doesn't matter the separation between
devDependencies and dependencies.
Updating the css-loader
Updating the fs-extra
Moving the utility packages to utils folder
Better description
Adds the license
closes #3
Write the env vars on the bundle file
http://dev.topheman.com/make-your-react-production-minified-version-with-webpack/
Fixs the hot reload setup
Sringifies the env object to define plugin
Uses the webpack html plugin to generate the pages in a less hacky way
Uses the write-file-webpack-plugin
this plugin allows the webpack write on disk all files, even running
with the webserver, which is necessary to the hot reload.
this plugin also help us to remove nasty hacks and expose bundles to
other extension features.
Allows exclude some entry points to be hot reloaded
It's useful for content scripts that can't keep the connection with the
webpack endpoint.
Updates the webpack
Updates the README with instructions about the content scripts
resolves #4
Updates to Webpack 2
closes #8
Expand the DefinePlugin usage
In Webpack 1, the replaced value at compile time by define plugin was placed with
parenthesis, like ({"NODE_ENV":"development","PORT":3000}), now, it not works in
this way, breaking the app.
So, to simplify the things, this commit just passes the NODE_ENV var.
Fix README
Exclude /node_modules/ from babel and css transpiling #9
Source maps to help debugging
closes #10
Removes the forbidden webpack config 'chromeExtensionBoilerplate'
before build and webserver's start
Although I know that it's not a good practice, right now I don't know a
good way to keep the boilerplate configs simple as it is today without
this hacky solution, so, until we came with a better solution, we'll
remove the key before build and webserver's start.
#9
Update README.md
Removing babel.js
Basically, we don't need transpiling with babel since Webpack 2 take care of
ES6 modules transpiling and the ES2015 is supported by Chrome.
kudos @gagarine
resolve #16
Setup boilerplate to load images and other assets in html and css
resolves #18
resolves #23
resolves #14
resolves #12
Added icons and images boilerplate
Split dependencies on package.json
resolves #15
Webpack config improvements (#26)
- Use CopyWebpackPlugin to generate `manifest.json` file
- Use CleanWebpackPlugin to clear build folder
Minor README adjustments
* explicitly the required node version
* pointing to yarn install instructions page instead suggest install
with npm. the yarn page will be always updated to the best way to install
the yarn.
closes #28
Adding the contribution guidelines
2016-04-14 06:16:50 -07:00
2019-01-06 14:15:53 -08:00
# Building extension
The most up-to-date instructions should be in [CI config ](./.circleci/config.yml ).
Collapse boilerplate in a single commit
First prototype
Added the README
Fixed the hot module replacement
Minor adjustments on readme
Normalizing the env vars and using it capitalized
Added info about the react.js branch
Fix babel transpiling
Using yarn
Removing the babel package, just the babel-core does the job
Using just the dependencies key on package.json
Since it isn't a lib package doesn't matter the separation between
devDependencies and dependencies.
Updating the css-loader
Updating the fs-extra
Moving the utility packages to utils folder
Better description
Adds the license
closes #3
Write the env vars on the bundle file
http://dev.topheman.com/make-your-react-production-minified-version-with-webpack/
Fixs the hot reload setup
Sringifies the env object to define plugin
Uses the webpack html plugin to generate the pages in a less hacky way
Uses the write-file-webpack-plugin
this plugin allows the webpack write on disk all files, even running
with the webserver, which is necessary to the hot reload.
this plugin also help us to remove nasty hacks and expose bundles to
other extension features.
Allows exclude some entry points to be hot reloaded
It's useful for content scripts that can't keep the connection with the
webpack endpoint.
Updates the webpack
Updates the README with instructions about the content scripts
resolves #4
Updates to Webpack 2
closes #8
Expand the DefinePlugin usage
In Webpack 1, the replaced value at compile time by define plugin was placed with
parenthesis, like ({"NODE_ENV":"development","PORT":3000}), now, it not works in
this way, breaking the app.
So, to simplify the things, this commit just passes the NODE_ENV var.
Fix README
Exclude /node_modules/ from babel and css transpiling #9
Source maps to help debugging
closes #10
Removes the forbidden webpack config 'chromeExtensionBoilerplate'
before build and webserver's start
Although I know that it's not a good practice, right now I don't know a
good way to keep the boilerplate configs simple as it is today without
this hacky solution, so, until we came with a better solution, we'll
remove the key before build and webserver's start.
#9
Update README.md
Removing babel.js
Basically, we don't need transpiling with babel since Webpack 2 take care of
ES6 modules transpiling and the ES2015 is supported by Chrome.
kudos @gagarine
resolve #16
Setup boilerplate to load images and other assets in html and css
resolves #18
resolves #23
resolves #14
resolves #12
Added icons and images boilerplate
Split dependencies on package.json
resolves #15
Webpack config improvements (#26)
- Use CopyWebpackPlugin to generate `manifest.json` file
- Use CleanWebpackPlugin to clear build folder
Minor README adjustments
* explicitly the required node version
* pointing to yarn install instructions page instead suggest install
with npm. the yarn page will be always updated to the best way to install
the yarn.
closes #28
Adding the contribution guidelines
2016-04-14 06:16:50 -07:00
2019-01-06 14:15:53 -08:00
You're gonna need `npm` for building extension.
Collapse boilerplate in a single commit
First prototype
Added the README
Fixed the hot module replacement
Minor adjustments on readme
Normalizing the env vars and using it capitalized
Added info about the react.js branch
Fix babel transpiling
Using yarn
Removing the babel package, just the babel-core does the job
Using just the dependencies key on package.json
Since it isn't a lib package doesn't matter the separation between
devDependencies and dependencies.
Updating the css-loader
Updating the fs-extra
Moving the utility packages to utils folder
Better description
Adds the license
closes #3
Write the env vars on the bundle file
http://dev.topheman.com/make-your-react-production-minified-version-with-webpack/
Fixs the hot reload setup
Sringifies the env object to define plugin
Uses the webpack html plugin to generate the pages in a less hacky way
Uses the write-file-webpack-plugin
this plugin allows the webpack write on disk all files, even running
with the webserver, which is necessary to the hot reload.
this plugin also help us to remove nasty hacks and expose bundles to
other extension features.
Allows exclude some entry points to be hot reloaded
It's useful for content scripts that can't keep the connection with the
webpack endpoint.
Updates the webpack
Updates the README with instructions about the content scripts
resolves #4
Updates to Webpack 2
closes #8
Expand the DefinePlugin usage
In Webpack 1, the replaced value at compile time by define plugin was placed with
parenthesis, like ({"NODE_ENV":"development","PORT":3000}), now, it not works in
this way, breaking the app.
So, to simplify the things, this commit just passes the NODE_ENV var.
Fix README
Exclude /node_modules/ from babel and css transpiling #9
Source maps to help debugging
closes #10
Removes the forbidden webpack config 'chromeExtensionBoilerplate'
before build and webserver's start
Although I know that it's not a good practice, right now I don't know a
good way to keep the boilerplate configs simple as it is today without
this hacky solution, so, until we came with a better solution, we'll
remove the key before build and webserver's start.
#9
Update README.md
Removing babel.js
Basically, we don't need transpiling with babel since Webpack 2 take care of
ES6 modules transpiling and the ES2015 is supported by Chrome.
kudos @gagarine
resolve #16
Setup boilerplate to load images and other assets in html and css
resolves #18
resolves #23
resolves #14
resolves #12
Added icons and images boilerplate
Split dependencies on package.json
resolves #15
Webpack config improvements (#26)
- Use CopyWebpackPlugin to generate `manifest.json` file
- Use CleanWebpackPlugin to clear build folder
Minor README adjustments
* explicitly the required node version
* pointing to yarn install instructions page instead suggest install
with npm. the yarn page will be always updated to the best way to install
the yarn.
closes #28
Adding the contribution guidelines
2016-04-14 06:16:50 -07:00
2019-01-06 14:15:53 -08:00
npm install
npm run build
After that you can find the extension in `build` directory and 'Load unpacked' if necessary. There is also Flow and Eslint set up.
Collapse boilerplate in a single commit
First prototype
Added the README
Fixed the hot module replacement
Minor adjustments on readme
Normalizing the env vars and using it capitalized
Added info about the react.js branch
Fix babel transpiling
Using yarn
Removing the babel package, just the babel-core does the job
Using just the dependencies key on package.json
Since it isn't a lib package doesn't matter the separation between
devDependencies and dependencies.
Updating the css-loader
Updating the fs-extra
Moving the utility packages to utils folder
Better description
Adds the license
closes #3
Write the env vars on the bundle file
http://dev.topheman.com/make-your-react-production-minified-version-with-webpack/
Fixs the hot reload setup
Sringifies the env object to define plugin
Uses the webpack html plugin to generate the pages in a less hacky way
Uses the write-file-webpack-plugin
this plugin allows the webpack write on disk all files, even running
with the webserver, which is necessary to the hot reload.
this plugin also help us to remove nasty hacks and expose bundles to
other extension features.
Allows exclude some entry points to be hot reloaded
It's useful for content scripts that can't keep the connection with the
webpack endpoint.
Updates the webpack
Updates the README with instructions about the content scripts
resolves #4
Updates to Webpack 2
closes #8
Expand the DefinePlugin usage
In Webpack 1, the replaced value at compile time by define plugin was placed with
parenthesis, like ({"NODE_ENV":"development","PORT":3000}), now, it not works in
this way, breaking the app.
So, to simplify the things, this commit just passes the NODE_ENV var.
Fix README
Exclude /node_modules/ from babel and css transpiling #9
Source maps to help debugging
closes #10
Removes the forbidden webpack config 'chromeExtensionBoilerplate'
before build and webserver's start
Although I know that it's not a good practice, right now I don't know a
good way to keep the boilerplate configs simple as it is today without
this hacky solution, so, until we came with a better solution, we'll
remove the key before build and webserver's start.
#9
Update README.md
Removing babel.js
Basically, we don't need transpiling with babel since Webpack 2 take care of
ES6 modules transpiling and the ES2015 is supported by Chrome.
kudos @gagarine
resolve #16
Setup boilerplate to load images and other assets in html and css
resolves #18
resolves #23
resolves #14
resolves #12
Added icons and images boilerplate
Split dependencies on package.json
resolves #15
Webpack config improvements (#26)
- Use CopyWebpackPlugin to generate `manifest.json` file
- Use CleanWebpackPlugin to clear build folder
Minor README adjustments
* explicitly the required node version
* pointing to yarn install instructions page instead suggest install
with npm. the yarn page will be always updated to the best way to install
the yarn.
closes #28
Adding the contribution guidelines
2016-04-14 06:16:50 -07:00
2019-01-06 14:15:53 -08:00
# Permissions used
* `notifications` for showing error notification
* `activeTab` for requesting url, title and selected text
2019-01-06 15:27:01 -08:00
* `http://localhost/capture` for talking with backend
Collapse boilerplate in a single commit
First prototype
Added the README
Fixed the hot module replacement
Minor adjustments on readme
Normalizing the env vars and using it capitalized
Added info about the react.js branch
Fix babel transpiling
Using yarn
Removing the babel package, just the babel-core does the job
Using just the dependencies key on package.json
Since it isn't a lib package doesn't matter the separation between
devDependencies and dependencies.
Updating the css-loader
Updating the fs-extra
Moving the utility packages to utils folder
Better description
Adds the license
closes #3
Write the env vars on the bundle file
http://dev.topheman.com/make-your-react-production-minified-version-with-webpack/
Fixs the hot reload setup
Sringifies the env object to define plugin
Uses the webpack html plugin to generate the pages in a less hacky way
Uses the write-file-webpack-plugin
this plugin allows the webpack write on disk all files, even running
with the webserver, which is necessary to the hot reload.
this plugin also help us to remove nasty hacks and expose bundles to
other extension features.
Allows exclude some entry points to be hot reloaded
It's useful for content scripts that can't keep the connection with the
webpack endpoint.
Updates the webpack
Updates the README with instructions about the content scripts
resolves #4
Updates to Webpack 2
closes #8
Expand the DefinePlugin usage
In Webpack 1, the replaced value at compile time by define plugin was placed with
parenthesis, like ({"NODE_ENV":"development","PORT":3000}), now, it not works in
this way, breaking the app.
So, to simplify the things, this commit just passes the NODE_ENV var.
Fix README
Exclude /node_modules/ from babel and css transpiling #9
Source maps to help debugging
closes #10
Removes the forbidden webpack config 'chromeExtensionBoilerplate'
before build and webserver's start
Although I know that it's not a good practice, right now I don't know a
good way to keep the boilerplate configs simple as it is today without
this hacky solution, so, until we came with a better solution, we'll
remove the key before build and webserver's start.
#9
Update README.md
Removing babel.js
Basically, we don't need transpiling with babel since Webpack 2 take care of
ES6 modules transpiling and the ES2015 is supported by Chrome.
kudos @gagarine
resolve #16
Setup boilerplate to load images and other assets in html and css
resolves #18
resolves #23
resolves #14
resolves #12
Added icons and images boilerplate
Split dependencies on package.json
resolves #15
Webpack config improvements (#26)
- Use CopyWebpackPlugin to generate `manifest.json` file
- Use CleanWebpackPlugin to clear build folder
Minor README adjustments
* explicitly the required node version
* pointing to yarn install instructions page instead suggest install
with npm. the yarn page will be always updated to the best way to install
the yarn.
closes #28
Adding the contribution guidelines
2016-04-14 06:16:50 -07:00
2019-01-06 14:15:53 -08:00
* `content_security_policy` needed for webpack.
Collapse boilerplate in a single commit
First prototype
Added the README
Fixed the hot module replacement
Minor adjustments on readme
Normalizing the env vars and using it capitalized
Added info about the react.js branch
Fix babel transpiling
Using yarn
Removing the babel package, just the babel-core does the job
Using just the dependencies key on package.json
Since it isn't a lib package doesn't matter the separation between
devDependencies and dependencies.
Updating the css-loader
Updating the fs-extra
Moving the utility packages to utils folder
Better description
Adds the license
closes #3
Write the env vars on the bundle file
http://dev.topheman.com/make-your-react-production-minified-version-with-webpack/
Fixs the hot reload setup
Sringifies the env object to define plugin
Uses the webpack html plugin to generate the pages in a less hacky way
Uses the write-file-webpack-plugin
this plugin allows the webpack write on disk all files, even running
with the webserver, which is necessary to the hot reload.
this plugin also help us to remove nasty hacks and expose bundles to
other extension features.
Allows exclude some entry points to be hot reloaded
It's useful for content scripts that can't keep the connection with the
webpack endpoint.
Updates the webpack
Updates the README with instructions about the content scripts
resolves #4
Updates to Webpack 2
closes #8
Expand the DefinePlugin usage
In Webpack 1, the replaced value at compile time by define plugin was placed with
parenthesis, like ({"NODE_ENV":"development","PORT":3000}), now, it not works in
this way, breaking the app.
So, to simplify the things, this commit just passes the NODE_ENV var.
Fix README
Exclude /node_modules/ from babel and css transpiling #9
Source maps to help debugging
closes #10
Removes the forbidden webpack config 'chromeExtensionBoilerplate'
before build and webserver's start
Although I know that it's not a good practice, right now I don't know a
good way to keep the boilerplate configs simple as it is today without
this hacky solution, so, until we came with a better solution, we'll
remove the key before build and webserver's start.
#9
Update README.md
Removing babel.js
Basically, we don't need transpiling with babel since Webpack 2 take care of
ES6 modules transpiling and the ES2015 is supported by Chrome.
kudos @gagarine
resolve #16
Setup boilerplate to load images and other assets in html and css
resolves #18
resolves #23
resolves #14
resolves #12
Added icons and images boilerplate
Split dependencies on package.json
resolves #15
Webpack config improvements (#26)
- Use CopyWebpackPlugin to generate `manifest.json` file
- Use CleanWebpackPlugin to clear build folder
Minor README adjustments
* explicitly the required node version
* pointing to yarn install instructions page instead suggest install
with npm. the yarn page will be always updated to the best way to install
the yarn.
closes #28
Adding the contribution guidelines
2016-04-14 06:16:50 -07:00
2019-01-06 14:15:53 -08:00
# Credits
* Icon made by < a href = "https://www.freepik.com/" title = "Freepik" > Freepik</ a > from < a href = "https://www.flaticon.com/" title = "Flaticon" > www.flaticon.com</ a > , licensed by < a href = "http://creativecommons.org/licenses/by/3.0/" title = "Creative Commons BY 3.0" target = "_blank" > CC 3.0 BY</ a >
* [Original Org Capture extension ](https://github.com/sprig/org-capture-extension )
* [Boilerplate for Webpack Chrome extension ](https://github.com/samuelsimoes/chrome-extension-webpack-boilerplate ))
