Robin Malfait 55aa4035f5 Fix format assumption when resolving module dependencies (#10878)
* fix assumption when resolving dependencies

When resolving dependencies given a path, we are only interested
relative files from the current file. We are not interested in the
dependencies that are listed in your `package.json` and thus in your
`node_modules` folder.

We made the assumption that your imports have at least 3 characters.
This sort of makes sense because there will be a `.`, then the OS
separator like `/` and than a file name. E.g.: `./a` is the minimal
amount of characters.

This makes sense for `import` statements, but in the case of `require`,
it is totally valid to write `require('.')`. This will require the
current `index.{js,ts,mjs,cjs,...}` in the current directory.

Before this change, having a `require('.')` wouldn't crash, but the
dependency would not be marked as a module dependencies and therefore we
won't listen for file changes for that dependency.

* update changelog
2023-03-27 19:41:20 +02:00
2023-03-27 14:59:41 +00:00
2023-03-24 10:44:18 -04:00
2023-02-08 17:39:43 +01:00
2023-01-13 12:22:00 +01:00
…
2022-02-05 15:22:47 -05:00
2023-03-27 14:59:41 +00:00
2023-03-24 07:45:03 +00:00
2023-01-20 18:34:29 +01:00

Tailwind CSS

A utility-first CSS framework for rapidly building custom user interfaces.

Build Status Total Downloads Latest Release License


Documentation

For full documentation, visit tailwindcss.com.

Community

For help, discussion about best practices, or any other conversation that would benefit from being searchable:

Discuss Tailwind CSS on GitHub

For casual chit-chat with others using the framework:

Join the Tailwind CSS Discord Server

Contributing

If you're interested in contributing to Tailwind CSS, please read our contributing docs before submitting a pull request.

S
Description
No description provided
Readme MIT
92 MiB
0 Stars 1 Watchers 0 Forks
Languages
TypeScript 80%
Rust 17.7%
JavaScript 0.7%
CSS 0.6%
HTML 0.6%
Other 0.4%