Skip to content

Wrong build when releasing package #440

@azygis

Description

@azygis

Describe the bug
I do not know what's happening differently from the regular build, but when package is released, it's seemingly does NOT output the correct structure compared to the regular npm run build:all. I saw a commit referencing wrong style import, but the fix was wrong as well. That makes it impossible to actually import the css files in consuming applications/packages. Maybe we can simply reference index.css since that at least matches in both builds? But that's a band-aid, the most important part is that the build does the same things, since now it seems to be doing something different (even though .release-it.json is supposed to run the build:all script).

Affected version(s)
At least 12.1.0, perhaps 12+ since that's when I made the treeshaking stuff.

To Reproduce
Steps to reproduce the behavior:

  1. Run npm run build:all locally
  2. Compare dist folder with the published package

Expected behavior
The structure should match, namely css files are different, not sure about the other files. Obviously, not talking about hashes in files, they're fine to be different.

Screenshots
When built locally, it looks like this:

Image

When released, it looks like this:

Image

Desktop (please complete the following information):
N/A

Smartphone (please complete the following information):
N/A

Additional context
N/A

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions