New api 4.0.1

[napsternxg]

This change uses the new API which has the backend and frontend code
separate. The code is now in three parts:

• core.js: has all the basic api code.
• background.js: uses API to create a background app.
• popup.js: uses API to create frontend app.
• All changes happen by using a call back to the storage sync functions.
• Fixes Deprecate the count key in storage #15 and Fixes Shift all the core code into a common file core.js #16

Other changes:

• Keyboard shortcut is Ctrl + Shift + L. Fixes Configurable keyboard shortcut for adding new pages to the list #4
• Updated manifest. Fixes Get rid of tabs / <all_urls> permissions #8
• package.json added
• Linter profile added. Fixes Add Linting profile #17

Fixes #4, #11, #14, #15, #16

• Better way to get filtered list of items for UI. Fixes Shift all the core code into a common file core.js #16
• Add title to list items. Fixes Add title text for links in the popup list.  #19
• Add some license details and headers to each of the files. Fixes Add headers to each file #20
• Allow download as JSON. Fixes Allow exporting and importing URLs from JSON format for safety. #13
• Make the title smaller on the popup. Saves space.
• Updated manifest.json
• Removed useless files.
• Cleaned up code using linter.
• Updated README

[kav2k]

I'm sorry, but have you tested it yourself?

You pushed out a broken update, 4.0.1 is nonfunctional.

I said I'd test it if I have time, but I haven't claimed I did by now:

the code is (presumably) working now
I'll do a testing run. If able, that is - I'll be quite busy until the end of next week.

[kav2k]

My apologies; I overreacted to this issue (due to misinterpreting what the error was).

4.0.1 was functional, but old data ("count") was causing trouble. It wouldn't be trivial to catch in testing.

[napsternxg]

No worries. The current version is 4.0.3 and works on my machine which has count, mix of old links without timestamp and new links with timestamp. In future, I wish to include a function which does some cleaning of the storage on the update of the API and removes these inconsistencies. That would require some work so I will leave of for later.

[kav2k]

I would recommend keeping the storage schema version in the storage, that removes the need for heuristics when you change the data format.