Closed pmienk closed 1 year ago
I wonder why node_modules
is committed into the repo.
I believe it shouldn't be like that.
@RobinTail - Required for github actions as documented.
@RobinTail - Required for github actions as documented.
I see exactly the opposite recommendation in the article you mentioned
Checking in your node_modules directory can cause problems. As an alternative, you can use a tool called @vercel/ncc to compile your code and modules into one file used for distribution.
@pmienk
I made some actions myself, and followed those recommendations on using ncc. There're also rollup and tsup suitable. Kindly suggesting you to consider committing the compiled js instead of node_modules.
Sounds like a worthwhile modification, and if you have experience with it I would happily take a working pull request.
It was not within the scope of my concern, namely fixing the problems referenced by this pull. As such I followed the path laid out by the originating repository.
It seems like using something like @vercel/ncc is preferred, but that is not in the scope of this PR, so should be fixed separately, IMO.
omg, it's already 2023 but these warnings are still unfixed.
I tried to fix all the warnings in @v1.2.1
release which is also available as @v1
. I think this PR can be closed. Please, feel free to open a new one or ping me here if you notice something unfixed.
Resolves #132 and #135