Config not found

[Ulyanov-programmer]

Hello!

In the process of using your library, I found an error that did not allow me to use it.

When importing the function:

import { cssToHtml } from 'css-to-html';

An error appears with content like:

"path_to_this/Config" not found (404)

This error appears both when I use the library separately (in node.js) and when I call it in the browser.

Perhaps you should specify the path to the imported file more precisely, because you have it, but the path to it is incorrect.

[Gigabyte5671]

Hi, thanks for letting me know about this!

This package relies on some browser-only JS features, so it currently doesn't work in Node.
(I've added a note to the readme to let others know about this limitation. Thanks!)

Regardless, I'll be able to take a closer look at your issue in a few hours. In the mean time, can you please share the steps you took to run this in your browser?

[Ulyanov-programmer]

I tried this:

0. I downloaded your library from npm and unpacked the dist folder locally.
1. I entered the following code in the .html file:

<script type="module">
  import { cssToHtml } from 'path_to_dist_of_css-to-html/index.js'

  const css = 'p { color: purple; }'
  cssToHtml(css).then((html) => {
    console.log(html)
  })
</script>

2. I ran this file in the browser and got this error seen in the console:

GET http://localhost:1243/assets/cssToHtml/Config net::ERR_ABORTED 404 (Not Found)

[Gigabyte5671]

Many thanks!

I was able to reproduce the issue. Turns out there was a typo in the Config module's import path.
Fixed with 1d07020.

Please let me know if you have any more issues.

[Ulyanov-programmer]

You definitely shouldn't rush into releases, because I found another bug!

I did the same thing, but got another error after launching:

Uncaught TypeError: Failed to resolve module specifier "css-selector-parser". Relative references must start with either "/", "./", or "../".

Apparently, this is happening here:

CSS-to-HTML/src/Generator.ts

Line 1 in 3e92f9d

import { createParser } from 'css-selector-parser';

This string is saved after compilation, which can be seen in the npm version.

If the library worked within the package manager, this would not be a mistake, but since it is supposed to work in the browser, he complains.

[Ulyanov-programmer]

In general, for the future: before closing an issue, ask its creator if it works for him.
This will protect you from many errors that could get into production.

[Gigabyte5671]

I appreciate the advice :)

However, that is not actually a bug. CSS-to-HTML is designed to be used with a bundler (eg, Vite, Webpack), not as a static script. Bundlers will include dependencies like this when building your app/website.

Perhaps this is really a bug with my documentation - I might add a section to the usage instructions explaining this.

[Ulyanov-programmer]

Yes, it is definitely worth adding a mention of this - it is not obvious from the description of the library at all.
Thank you for your prompt response!

[Gigabyte5671]

Hi again!

I've just added support for using CSS-to-HTML as a static script with version 0.8.0.

[Ulyanov-programmer]

Great! But I don't really need it, because I am the developer of an alternative solution css2html that works with node.js (I only found out about the existence of your library when I wanted to publish my package, as it turned out, under your name), therefore, I will limit my help. :]

[Gigabyte5671]

All good! Good luck with your library :)