1. The library should be significantly or extremely customisable, fast, reliable, flexible, easy to use.

2. It should be free from any errors, bottlenecks, edge cases, memory leaks, information leaks, resources consumption, issues.

3. It should be as robust and refined as possible.

4. Implement all of the best practices you know about appropriately.

5. The library should be a scrapper library which can significantly to get the necessary scraped data using css selectors.

6. It should support multiple urls with their different css selectors.

7. In input it should take The Url to scrap, the css selectors for only this url and a Proxy url if necessary.

8. The library output should be the fully parsed extracted data which user get in dom or as json or as in indexdb or in dexie or log easily.

9. It should secure and fast.

10. User should be able to customise library settings like on/off use strict for parsing, on/off of to fetch different contents from different url at once, to cache or not, different user agents for different urls, if to send 'since modified' header before request or not on different urls and many more.

11. It should fetch all of the seprate html content of all the urls, then remove all of the js and CSS codes from it, then prevent attacks, then parse the whole html content, then convert them into dom, extract all of the data using CSS selectors, then send all of the data in appropriate way according to user.

12. Don't mix up any url with another or any html content with another or any css selectors with other, and so on.

13. It should avoid duplication and should be ready to handle potential possible issues including null value or null url or null selectors or invalid url or invalid selectors.

14. Use only the best practices possible.

15. I want a state-of-the-art piece.

16. Don't compromise.

17. Make it extremely easy to use.

18. I want the best possible solution you can make and I mean it.

19. When loaded it should be globally available.

20. Handle all of the errors appropriate as they should.

21. Always consider and handle all of the potential or possible edge cases, bottlenecks, loopholes, errors, memory leaks, what if scenarios, resources consumption, any issue in any process.

22. With this try to make the web scraping easy as possible.

23. It should support proxy and should use it appropriately.

24. Make sure user can customise different Cors proxy urls for for different urls, to be able to on or off corsproxy urls usage on any url.

25. Improve and make it better.

26. Think step by step.

27. Do whatever you want I just want a satisfying results.

28. Review your whole approach again and then Improve it even further appropriately.

29. Make this work properly in any circumstances.

30. Make sure all of things should be used and works appropriately including proxy url.

31. Review your whole approach or codes plan or solutions again for any issues or can be better and fix them.

32. Reinforce it further.

33. Make this work.

34. Keep it straight forward yet very powerful, customisable, flexible, reliable, fast in any circumstances.

35. Don't make it unnecessarily complicated.

36. This library is for client side web scraping only and can be used in any web apps or web sites. Don't add anything that needs an backend or a server to work. This is not for server side.

37. Make this library practically feasible. Make this work in real world scenerios. I Don't want basic version or example. Client side solutions only.

38. Make sure user can customise if to enable proxie url for a specific url or globally across all the urls, if to applie all of the customisable settings across all of the urls globally like user agent, custom headers, if to enable cache globally or on specific urls, and so on.

39. Make sure user customise if to applie any settings globally across all urls, or in which db do user want's the response in, or applie it globally or specificly as how user wants the response as from any urls.

40. Make sure user applie the configuration across all urls or individual urls.

41. Make this real and practically feasible as however you can.

42. Remove everything like the fetched html content, extract data from the library after successfully processing and sending the response immediately to the user.

43. Make sure it support streaming of the extracted data.

44. Reenforce it further.

45. I want the best or satisfactory results only.

46. Send the fully 'working' full codes in one js file.