Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Merge from internal & fixup .npmrc #150

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Jul 6, 2022
Merged

Merge from internal & fixup .npmrc #150

merged 5 commits into from
Jul 6, 2022

Conversation

wtgodbe
Copy link
Contributor

@wtgodbe wtgodbe commented Jun 24, 2022

Merged in the missing internal commit, and then updated the file as per https://github.com/dotnet/arcade-services/pull/1924/files

MerlinBot and others added 2 commits June 24, 2022 16:20
…nst potential Software Supply Chain attacks. This starts with ensuring your repository has a valid Azure Artifacts configuration so you can take advantage of [Central Feed Services](https://aka.ms/cfs). We are opening this PR with a fix on known issue(s) which we have detected in your repository. Please review and approve this PR at your earliest convenience.

**This may impact the ability for pipelines and developers to install packages and build projects.**

## Address **breaking changes** before you merge:
* Confirm the suggested Feed is configured per your organization's guidelines. If changes are necessary, work with your Project Administrators to set it up correctly.  [Learn more...](https://docs.microsoft.com/en-us/azure/devops/artifacts/feeds/feed-permissions?view=azure-devops)
* Add authentication to any failing pipeline definitions. [nuget](https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/package/nuget-authenticate?view=azure-devops), [npm](https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/package/npm-authenticate?view=azure-devops).
* Reach out to developers who may need to authenticate to the feed using the [internal_PublicPackages's Connect to feed](https://dev.azure.com/dnceng/internal/_artifacts/feed/internal_PublicPackages/connect) instructions in Azure Artifacts.

## Changes
* `.npmrc` added as a sibling to this [package.json](/package.json) referencing [internal_PublicPackages](https://dev.azure.com/dnceng/internal/_artifacts/feed/internal_PublicPackages) feed

### Still stuck?
Reach out to [email protected] with any questions.

---

This change was automatically generated by [1ES Gardener](https://www.1eswiki.com/wiki/1ES_Gardener) which is an initiative by the 1ES team to help repos stay up-to-date with latest tools, features, and best practices. For feedback or questions, please contact the [Gardener team](mailto:[email protected]).
@wtgodbe wtgodbe requested a review from dougbu June 28, 2022 16:07
@wtgodbe
Copy link
Contributor Author

wtgodbe commented Jun 28, 2022

I believe merge-committing this will unblock the mirror (CC @dougbu)

@wtgodbe wtgodbe changed the title Merge from internal Merge from internal & fixup .npmrc Jun 28, 2022
@dougbu
Copy link
Member

dougbu commented Jun 28, 2022

This apparently isn't a solution when building in public. /cc @mmitche

C:\Program Files\dotnet\sdk\6.0.301\MSBuild.dll -consoleloggerparameters:Summary -maxcpucount -property:SignType= -property:Configuration=Release -restore -verbosity:m /bl:artifacts/logs/build.binlog .\build.proj
  Determining projects to restore...
  Restored D:\a\1\s\build.proj (in 182 ms).
  npm WARN [email protected] license should be a valid SPDX license expression
  
  npm ERR! code E401
  npm ERR! Unable to authenticate, your authentication token seems to be invalid.
  npm ERR! To correct this please trying logging in again with:
  npm ERR!     npm login
  
  npm ERR! A complete log of this run can be found in:
  npm ERR!     C:\npm\cache\_logs\2022-06-28T16_08_19_154Z-debug.log
D:\a\1\s\build.proj(30,9): error MSB3073: The command "npm install" exited with code 1.

@dougbu
Copy link
Member

dougbu commented Jul 6, 2022

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@dougbu
Copy link
Member

dougbu commented Jul 6, 2022

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mmitche
Copy link
Contributor

mmitche commented Jul 6, 2022

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@dougbu
Copy link
Member

dougbu commented Jul 6, 2022

We have a few warnings that could be addressed here or later:

  npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
...
EXEC : warning : NU5125: The 'licenseUrl' element will be deprecated. Consider using the 'license' element instead. [D:\a\1\s\build.proj]
EXEC : warning : NU5048: The 'PackageIconUrl'/'iconUrl' element is deprecated. Consider using the 'PackageIcon'/'icon' element instead. Learn more at https://aka.ms/deprecateIconUrl [D:\a\1\s\build.proj]

The first is a simple change to build.proj, as the warning suggests.

The second is pretty simple too: <license type="expression">MIT</license>.

I also recommend using "license": "MIT" in the package.json file. (It also feels odd that the license here is the MIT URI while the npm package points to https://aka.ms/jqueryunobtrusivelicense. That URI redirects back to https://github.com/aspnet/jquery-validation-unobtrusive/blob/main/LICENSE.txt and displays the MIT license content but why have the indirection❔ Using the license expression in both places would be better.)

The last one requires a slight change to the .nuspec to add the icon file (which isn't in the repo yet) and doing the right stuff to reference it. We have done that elsewhere, even w/o Arcade's help (though that does make it much easier.)

@wtgodbe wtgodbe merged commit e1d920b into main Jul 6, 2022
@wtgodbe wtgodbe deleted the wtgodbe/Morg2 branch July 6, 2022 22:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants